[seam-issues] [JBoss JIRA] Commented: (SOLDER-100) Missing deps running in Weld SE

[Peter Royle (JIRA)]

    [ https://issues.jboss.org/browse/SOLDER-100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12593667#comment-12593667 ] 

Peter Royle commented on SOLDER-100:
------------------------------------

Stack for LogManager:

Exception in thread "main" com.google.common.collect.ComputationException: java.lang.NoClassDefFoundError: org/jboss/logmanager/Level
        at com.google.common.collect.MapMaker$StrategyImpl.compute(MapMaker.java:602)
        at com.google.common.collect.MapMaker$StrategyImpl.compute(MapMaker.java:462)
        at com.google.common.collect.CustomConcurrentHashMap$ComputingImpl.get(CustomConcurrentHashMap.java:2045)
        at org.jboss.weld.resources.ClassTransformer.loadClass(ClassTransformer.java:164)
        at org.jboss.weld.bootstrap.BeanDeployer.addClass(BeanDeployer.java:61)
        at org.jboss.weld.bootstrap.BeanDeployer.addClasses(BeanDeployer.java:88)
        at org.jboss.weld.bootstrap.BeanDeployment.deployBeans(BeanDeployment.java:134)
        at org.jboss.weld.bootstrap.WeldBootstrap.deployBeans(WeldBootstrap.java:377)
        at org.jboss.weld.environment.se.Weld.initialize(Weld.java:79)
        at org.jboss.weld.environment.se.StartMain.go(StartMain.java:45)
        at org.jboss.weld.environment.se.StartMain.main(StartMain.java:57)



> 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