JBossDeveloper

Would you like for us to try to get the current file structure to work with maven?

It would be better, for maven users, to have seam examples with the maven file structure instead of the current one.

guys...let's just get the "use seam with maven" solved first, right ? :)

A couple of weeks ago I started a small project using Seam. Since I don't like to include all-in-one jars to resolve dependencies, I went through the process of manually adding each and every dependency.

I don't use the jBPM stuff but the I have reviewed the other dependencies and arrived at a minimal set that allows me to compile my code which includes ajax4jsf, facelets, seam, ejb3, jpa and hibernate-annotations. I've tried to add information about whether the dependency is compile-time and/or run-time, whether it is provided by the container (JBoss), the version and related dependencies, etc. There still might be a lot missing though.

The EJB3 api is provided by the jboss-ejb3x.jar in the ${jboss.home}/server/default/deploy/ejb3.deployer directory. The JPA api is provided by the ejb3-persistence.jar in the ${jboss.home}/server/default/lib directory.

Of course, using the JSF 1.2 RI gives a little bit of a different set.

Finally, a little bit off topic but I believe that the EAR level dependencies (jboss-seam.jar, el-api.jar, el-ri.jar) should be packaged in a directory called 'lib' (can be overridden) within the EAR file and not be included through the in application.xml. This is intended for application-clients.

That last statement is correct, shared libs in an EAR go into EAR/lib/ in Java EE 5.0.

However, in J2EE 1.4 and JBoss 4.0, you need to use a MANIFEST.MF in the ejb.jar and web.war archives, and reference the shared library by name in a Classpath: entry. Make sure that you have a new line after this, and that there is something in that new line (like a Created-By: entry). This is totally broken stuff in J2EE 1.4. I've lost a lot of hair until I figured that one out.

The way most Seam examples declare shared JARs in an EAR now, via a client module in application.xml, is not really correct and slower (these JARs are scanned by deployers), but seems to work.

I forgot to mention that I updated the dependencies list on the wiki.

As with the ear-scoped libraries. Ant 1.7.0 now provides support for auto-generating the manifest entries.

I have a child coming up so I won't spend much time either. Still, let me know if I can help.

"mzeijen" wrote:
2. Find out how we can make it easy for the users to cope with those annoying javax.{library} libraries that aren't allowed in public Maven2 repositories because of their license.