Seam Tomcat Deployment: EJB beans contained in non-application JARs

[nikolay.chorniy]

Hi everyone!

I have a problem in project deployment. For technical requirements of Seam 1.2.1 GA based project I develop, Tomcat deployment with EJB3 enabled is used.
The result war file structure looks like this:

application.war
|
- WEB-INF
|    |
|    - components.xml
|    - web.xml
|    - pages.xml
|    |
|    - lib
|    |   |
|    |    - application.jar
|    |      - ... {EJB bean classes}
|    |       - seam.properties
|    |       - META-INF
|    |           |
|    |           - ejb-jar.xml
|    |           - jboss-beans.xml
|    |           - persistence.xml
|    |      
|    |    - entities.jar
|    |       -... {Entity bean classes}
|    |       - seam.properties

The problem is that all EJB beans contained in application.jar are deployed, but entity beans in entities.jar are not deployed, though JBoss MicroContainer determines that file (seam.properties is included).
Copying entities.jar file content to application.jar solves the problem (EJB entitiy beans are deployed), but that is surely far from smart.

Thanks a lot for any help!

[pmuir]

For JPA to scan a jar for entities, the jar must contain a META-INF/persistence.xml - otherwise, list out the entites in persistence.xml