If I wrap all the entity beans into a *..ejb3 file and then deploy the file to /server/default/deploy it all seems to work fine.
However, this forces me to use the system default values (no persistence.xml).
Is there any way to deploy a *.par file directly without putting it in an *.ear file?
1) You should be able to put a persistence.xml file within a .ejb3 file and deploy EJBs along with persistent entities. This is not spec compliant, but it is what we will support in JBoss.
2) You should be able to deploy a .par on its own.
If you are not able to do #1 and #2 then please log a JIRA bug.
I was not able to deploy a seperate *.par for my application. I may have some configuration error.
As a test I will break apart the *.ear file for TrailBlazer application and see if I can depoly seperate *.par and *.ejb3 files.
I'll let you know how this goes later tonight.
When I break apart the EJB3Trail.ear and place the components in /opt/jboss/server/default/deploy, I get the following error.
javax.naming.NameNotFoundException: managedEntityFactory.cal not bound
I am not sure if this is a bug in JBoss or a configuration error on my part.
I am placing the application.xml in /opt/jboss/server/default/deploy/EJB3Trail/META-INF
Should this work?
I also encouonterd a similer problem while trying to deploy all my entities and session beans in the ejb3, but persistance.xml dosent seems to work. In that case I need to make entries in persistance.properties.