Does a PAR have to reside in an EAR?

[bill.burke]

Typo? The unitName in @PErsistenceContext and the name defined in persistence.xml don't match. Is this your problem?

[platinumdragon]

Good catch, thank you, but no. It's a typo. They are both envEM.

[bill.burke]

how is your application.xml/jboss-app.xml set up?
what is the structure of your ear?

[platinumdragon]

I am trying to avoid doing an EAR. I would like to have individual PAR/EJB3 files in a subdirectory of deploy:

deploy/
deploy/test/
deploy/test/environment.par
deploy/test/this-business.par
deploy/test/that-business.ejb3

so that I can replace, or add new functionality dynamically. I would actually like the stateless bean above to be a JMX Service instead, but I am just trying to get it to work now.

I don't have an application.xml or jboss-app.xml. Just the Environment interface, EnvironmentBean class, and persistence.xml file. There is a similar par in the trailblazer, but it is within an EAR, which I am hoping to avoid.

Thanks,
Mike

[platinumdragon]

Incidentally, if I comment out the @PersistenceContext line, it deploys fine.

[platinumdragon]

So.. nobody knows, huh?

[bill.burke]

looks like the .ejb3 file is being deployed before the PARs. I don't have any automatic dependency management at the moment. if you package this stuff in an EAR you can define the deployment order (the order the module's are specified). This may solve your problem.

I'm on vacation this week so won't be able to dive in til next week or later.

Bill

[msly]

I noticed the same issue. If I restart the server the ejb3 archive tries to load first and says that the entities in the par file are not bound. Should we post this issue in the design forum?

[goeh]

I also had the same issue, but found a workaround.
I placed all my entities in a .ejb3 archive with a name that deployed before my session beans archive. Then it all worked. I know that this is not by the spec, but it seems to works with 4.0.3 RC1 and RC2.