6:57 a.m.
[
https://issues.jboss.org/browse/SOLDER-100?page=com.atlassian.jira.plugin...
]
Peter Royle commented on SOLDER-100:
------------------------------------
Stack trace for missing Servlet API (prob not very helpful, it just shows Weld SE
struggling to load ServletContextListener on behalf of solder's
servlet/ResourceListener:
217 [main] ERROR org.jboss.weld.environment.se.discovery.Scanner - Error loading
org/jboss/seam/solder/resourceLoader/servlet/ResourceListener.class
java.lang.NoClassDefFoundError: javax/servlet/ServletContextListener
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClassCond(ClassLoader.java:632)
at java.lang.ClassLoader.defineClass(ClassLoader.java:616)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:283)
at java.net.URLClassLoader.access$000(URLClassLoader.java:58)
at java.net.URLClassLoader$1.run(URLClassLoader.java:197)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
at
org.jboss.weld.environment.se.discovery.AbstractScanner.handle(AbstractScanner.java:51)
at
org.jboss.weld.environment.se.discovery.URLScanner.handleArchiveByFile(URLScanner.java:149)
at org.jboss.weld.environment.se.discovery.URLScanner.handle(URLScanner.java:126)
at
org.jboss.weld.environment.se.discovery.URLScanner.scanResources(URLScanner.java:107)
at
org.jboss.weld.environment.se.discovery.SEWeldDiscovery.scan(SEWeldDiscovery.java:71)
at
org.jboss.weld.environment.se.discovery.SEWeldDiscovery.<init>(SEWeldDiscovery.java:45)
at
org.jboss.weld.environment.se.discovery.SEBeanDeploymentArchive$1.<init>(SEBeanDeploymentArchive.java:45)
at
org.jboss.weld.environment.se.discovery.SEBeanDeploymentArchive.<init>(SEBeanDeploymentArchive.java:44)
at
org.jboss.weld.environment.se.discovery.SEWeldDeployment.<init>(SEWeldDeployment.java:37)
at org.jboss.weld.environment.se.Weld$1.<init>(Weld.java:73)
at org.jboss.weld.environment.se.Weld.initialize(Weld.java:72)
at org.jboss.weld.environment.se.StartMain.go(StartMain.java:45)
at org.jboss.weld.environment.se.StartMain.main(StartMain.java:57)
Caused by: java.lang.ClassNotFoundException: javax.servlet.ServletContextListener
at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
at java.lang.ClassLoader.loadClass(ClassLoader.java:248)
... 25 more
Missing deps running in Weld SE
-------------------------------
Key: SOLDER-100
URL: https://issues.jboss.org/browse/SOLDER-100
Project: Seam Solder
Issue Type: Enhancement
Affects Versions: 3.0.0.CR4
Reporter: Peter Royle
Priority: Minor
Labels: dependencies, runtime, weld, weld-se
My main concern is the runtime dependency on javax.servlet API when run in Weld SE.
Fundamentally if you wish to target SE it shouldn't bomb out when servlet is not on
the classpath. We had a similar issue with Weld SE at the beginning as well, and Pete Muir
sorted it out. Unfortunately this problem doesn't occur when using Arquillian's
Weld SE configuration, so I don't have a sample test to give you.
This was the dependency I added to solve that particular problem:
<dependency>
<groupId>javax.servlet</groupId>
<artifactId>servlet-api</artifactId>
<version>2.5</version>
</dependency>
There were also other runtime dependencies which weren't satisfied when running in
Weld SE. These solved them:
<dependency>
<groupId>org.jboss.logmanager</groupId>
<artifactId>jboss-logmanager</artifactId>
<version>1.2.0.CR9</version>
</dependency>
<dependency>
<groupId>log4j</groupId>
<artifactId>log4j</artifactId>
<version>1.2.14</version>
</dependency>
I'll provide stack traces for each of the individual errors in separate comments.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira