I am attempting to deploy an EAR containing two jars.

Common.jar contains a table User.

App.jar contains tables that have createUser and lastUpdateUser columns.

Common.jar contains embeddables (CreateAudit, UpdateAudit) with a many-to-one join on the user id.

These embeddables are used in the entities in App.jar.

Oh: and we are using annotations.

When I deploy the ear to JBoss, it complains that the tables in App.jar refer to a nonexistent entity named User.

Both jars have a persistence.xml that sets the persistence-unit to "DefaultPersistenceUnit". Should I set them to different units and somehow tell the many-to-one join that it always joins to the "common" persistence unit? Is it not do-able at all?

Ok.

I think the way to go is that the persistence.xml needs to contain a jar-file section so that both jars get loaded into the persistence unit.

However, I am coming across a weird bug. When my persistence xml contains


jboss whinge that it cannot find the jar file, and the reason it can't find it is that it is looking in the Jboss bin directory (!!!!).

Let's see if jboss 4.0.5 fixes this.