I have a MDB marked with #Depends making it dependent on my war, when I deploy the application to the server it works ok, but when I try to run my tests the test fails...seams because of some wrong config...any hints to solve this? I guess that the embeded jboss handels this in some diferent way?
I use: seam 2.2.1 jboss 5.1 testNG
the Error when I run the test :
FAILED CONFIGURATION: #BeforeSuite startSeam
org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
CONTEXTS MISSING DEPENDENCIES: Name -> Dependency{Required State:Actual State}
jboss.j2ee:jar=classes,name=DlqHandler,service=EJB3
-> <UNKNOWN>{Described:** UNRESOLVED Demands 'jboss.web.deployment:war=convert_it/ **}
jboss.j2ee:jar=classes,name=ImageConverterMDB,service=EJB3
-> <UNKNOWN>{Described:** UNRESOLVED Demands 'jboss.web.deployment:war=convert_it/ **}
jboss.j2ee:jar=classes,name=VideoConverterMDB,service=EJB3
-> <UNKNOWN>{Described:** UNRESOLVED Demands 'jboss.web.deployment:war=convert_it/ **}
Related
Current jetty version is 9.4.6, I tried to upgrade 9.4.44, I got the error. Could you please help me?
WebAppContext:554 -Failed startup of context o.e.j.w.WebAppContext#163f1cd{passwd-change,/passwd-change,file:///run/opt/corp/gsec/7.0.0/java-service/gsec-jetty-base/temp/jetty-gsec-2443-passwd-change.war-_passwd-change-any-6326268666909012254.dir/webapp/,UNAVAILABLE}{/passwd-change.war}
Caused by: java.lang.IllegalAccessError: tried to access method org.eclipse.jetty.server.handler.ContextHandler$StaticContext.createInstance(Ljava/lang/Class;)Ljava/lang/Object; from class jetty.webapp.StandardDescriptorProcessor
at org.eclipse.jetty.webapp.StandardDescriptorProcessor.newListenerInstance(StandardDescriptorProcessor.java:1945) ~[apacheds-service-2.0.0-M24.jar:2.0.0-M24]
at org.eclipse.jetty.webapp.StandardDescriptorProcessor.visitListener(StandardDescriptorProcessor.java:1900) ~[apacheds-service-2.0.0-M24.jar:2.0.0-M24]
The jetty files in your apacheds-service-2.0.0-M24.jar needs to be upgraded as well.
List the contents of the apacheds-service-2.0.0-M24.jar file and you'll see classes in the org.eclipse.jetty. namespace.
Those are conflicting with your efforts to upgrade Jetty via the jetty-distribution zip.
I had a different setup that triggered a similar stacktrace: using cargo-maven2-plugin 16.1 in a spring 5 project, mvn cargo:run would fail because of a conflict with javafx.base-11.0.0-SNAPSHOT.jar files.
Upgrading to cargo-maven3-plugin 1.9.9 fixed the matter.
I'd encourage who ever uses cargo-maven2-plugin to migrate to cargo-maven3-plugin as the doc states:
Please be aware that the Maven 2 / Maven 3 plugin of Codehaus Cargo has been retired with our version 1.9.0 and has been superseded by a Maven 3 only plugin.
I'm trying to mock a Teaser class (public interface) using mockito core 3.8 and I'm not able to do it.
I've JAVA 11 and this is the following error:
org.mockito.exceptions.base.MockitoException:
Mockito cannot mock this class: interface com.adobe.cq.wcm.core.components.models.Teaser.
Mockito can only mock non-private & non-final classes.
If you're not sure why you're getting this error, please report to the mailing list.
Java : 11
JVM vendor name : Oracle Corporation
JVM vendor version : 11.0.12+8-LTS-237
JVM name : Java HotSpot(TM) 64-Bit Server VM
JVM version : 11.0.12+8-LTS-237
JVM info : mixed mode
OS name : Windows 10
OS version : 10.0
Underlying exception : java.lang.IllegalStateException: Type not found: com.adobe.cq.wcm.core.components.internal.jackson.ComponentDataModelSerializer
What's happening here?
I finally got a solution for this.
The problem was that I didn't had wcm core components dependency on my project. Since AEMaaCS includes that dependency as a package, we didn't need to include the dependency in our project.
I ended up adding the dependency but just for the scope=test.
While building an Angular 6 app i get a compile error in #angular/core/src/render3/interfaces on line 35. The line is:
[ACTIVE_INDEX]: number | null;
and the error is:
error TS1169: A computed property name in an interface must directly refer to a built-in symbol.
I an using #angular/core#6.1.6. Am I doing something wrong or is this an Angular bug?
Verify that Visual Studio is targeting the correct version of Typescript (as seen in your package.json), then try deleting your node_modules folder, and rerunning npm install.
I believe that this is caused by running Angular 6 with an earlier, incompatible version of typescript (<2.7), because it looks like the ability used by the container.d.ts file (referenced in your error) to use Constant-Named Properties was added in Typescript 2.7. Of course, if it were that simple then ng serve would tell you about the Typescript incompatibility, so I assume that I'm either wrong, or that your environment is playing tricks on you.
See here for a related question.
I installed sbt in my windows 7 machine from http://www.scala-sbt.org/0.13/docs/Installing-sbt-on-Windows.html using msi installer
After installing if i go to Command prompt and while checking the installed sbt version i get the below error
C:\>sbt --version
Getting org.fusesource.jansi jansi 1.11 ...
:: problems summary ::
:::: WARNINGS
module not found: org.fusesource.jansi#jansi;1.11
==== local: tried
C:\Users\rajasure\.ivy2\local\org.fusesource.jansi\jansi\1.11\ivys\ivy
.xml
-- artifact org.fusesource.jansi#jansi;1.11!jansi.jar:
C:\Users\rajasure\.ivy2\local\org.fusesource.jansi\jansi\1.11\jars\jan
si.jar
==== Maven Central: tried
https://repo1.maven.org/maven2/org/fusesource/jansi/jansi/1.11/jansi-1
.11.pom
-- artifact org.fusesource.jansi#jansi;1.11!jansi.jar:
https://repo1.maven.org/maven2/org/fusesource/jansi/jansi/1.11/jansi-1
.11.jar
==== typesafe-ivy-releases: tried
https://repo.typesafe.com/typesafe/ivy-releases/org.fusesource.jansi/j
ansi/1.11/ivys/ivy.xml
==== sbt-ivy-snapshots: tried
https://repo.scala-sbt.org/scalasbt/ivy-snapshots/org.fusesource.jansi
/jansi/1.11/ivys/ivy.xml
::::::::::::::::::::::::::::::::::::::::::::::
:: UNRESOLVED DEPENDENCIES ::
::::::::::::::::::::::::::::::::::::::::::::::
:: org.fusesource.jansi#jansi;1.11: not found
::::::::::::::::::::::::::::::::::::::::::::::
:::: ERRORS
Server access Error: Connection timed out: connect url=https://repo1.mav
en.org/maven2/org/fusesource/jansi/jansi/1.11/jansi-1.11.pom
Server access Error: Connection timed out: connect url=https://repo1.mav
en.org/maven2/org/fusesource/jansi/jansi/1.11/jansi-1.11.jar
Server access Error: Connection timed out: connect url=https://repo.type
safe.com/typesafe/ivy-releases/org.fusesource.jansi/jansi/1.11/ivys/ivy.xml
Server access Error: Connection timed out: connect url=https://repo.scal
a-sbt.org/scalasbt/ivy- snapshots/org.fusesource.jansi/jansi/1.11/ivys/ivy.xml
:: USE VERBOSE OR DEBUG MESSAGE LEVEL FOR MORE DETAILS
unresolved dependency: org.fusesource.jansi#jansi;1.11: not found
Error during sbt execution: Error retrieving required libraries
(see C:\Users\suren\.sbt\boot\update.log for complete log)
Error: Could not retrieve jansi 1.11
Could somebody help me on fixing this error? I really need some help on this.
I had the same problem! this solved!
" Looks like the dependency manager has a problem with the non-ASCII characters in your user name.
Try adding -Dsbt.global.base=C:/some/other/path to the command line of the SBT process. This will relocate files from the default location of %USERHOME%/.sbt. "
Since we migrate from CQ5.6.1 to AEM6.1 we have some difficulties to start our bundles :
17.08.2015 16:23:26.385 *ERROR* [qtp2140358820-67] org.apache.felix.http.jetty %bundles.pluginTitle: Cannot start (org.osgi.framework.BundleException: Unresolved constraint in bundle com.mybundle.core [477]: Unable to resolve 477.0: missing requirement [477.0] osgi.wiring.package; (&(osgi.wiring.package=com.adobe.granite.xss)(version>=1.0.0)(!(version>=2.0.0))))
org.osgi.framework.BundleException: Unresolved constraint in bundle com.mybundle.core [477]: Unable to resolve 477.0: missing requirement [477.0] osgi.wiring.package; (&(osgi.wiring.package=com.adobe.granite.xss)(version>=1.0.0)(!(version>=2.0.0)))
But when I look at the bundles console, under "Adobe Granite XSS Protection (com.day.cq.cq-xssprotection)" I see the right version exported :
Exported Packages com.adobe.granite.xss,version=1.1.0
com.day.cq.xss,version=5.4.0
com.day.cq.xss.taglib,version=5.4.0
org.apache.sling.xss,version=1.0.0
The problem seems to be random (the exact same code and AEM version and java version works well on another pc)
Does anybody encountered the same issue ?