I encountered a weird issue when deploying one of the modules of our project on a JBossAS6-Final after I had just added Seam 3 as a dependency to the Maven POM file.

There seems to be a conflict between Seam Solder and the JODReports library, that itself depends on jython and freemarker. The deployment fails with a NoClassDefFoundError caused by a missing class org.python.core.PyException. In an attempt to solve this I explicitly added jython 2.2 as a dependency to the pom, but the deployment now fails with a NoClassDefFoundError caused by freemarker.ext.jdom.NodeListModel$AttributeXMLOutputter. This is strange, because this class is clearly part of the deployed package. Somehow, just adding Seam Solder to the project prevents a class on the classpath from being loaded. In the maven tree no conflicts are visible.

I have stripped down the module to the simplest pom file that can still reproduce the issue. Can someone explain me what's happening and - if possible - how I can find a workaround? It is currently blocking us from using Seam 3. To reproduce the error I deployed a package that was built with the following pom.xml and contained a single EJB with a local interface and nothing more than a doNothing() method.

No it's a jar that in the real project bundles EJB's. The dependent libraries are included using the maven shade plugin.

The complete project is of course much too big to post on this forum, but just this pom is already enough to produce a jar package that can not be deployed on JBoss6. You can build it by running 'mvn package' in the directory where you placed the pom file.

Thank you very much for your help, it helped me solve the problem. By changing the packaging to war it worked.

Deploying just a jar file on JBossAS6 is perfectly possible for a EJB3 package. At least, that's what we've been doing for the last 6 months.But apparently it is not possible to use Weld inside such a package...