Persistence unit deployers are not invoked for WEB-INF/lib j

[wolfc]

A persistence unit can be packaged in a jar in WEB-INF/lib (JPA 6.2).
Right now the persistence unit deployers are not invoked when this is the case.

[alesj]

"wolfc" wrote:
A persistence unit can be packaged in a jar in WEB-INF/lib (JPA 6.2).
Right now the persistence unit deployers are not invoked when this is the case.

Can you describe a bit more what you expect to get,
e.g. what's the metadata we need to create - URL to be passed to ORM, ...

Or what's stopping you to write such deployer,
which would check WEB-INF/lib jars for persistence.xml (or whatever describes persistennce unit)?
What's so different from what you already wrote - your JpaDeployer?

[wolfc]

I already have such a deployer, it's the PersistenceParsingDeployer.

I just need something that triggers this deployer.
Maybe the WARStructure can fire something off?
It's similar to deploying an EAR with modules in it, but for JavaEE 5 most 'module' types should be ignored.

[alesj]

"wolfc" wrote:

I just need something that triggers this deployer.

You could check all WEB-INF/lib jars for it
and create something useful.
Or create new structure - PersistenceUnitStructure.

I'm saying this w/o having any idea what the spec requires. ;-)

"wolfc" wrote:

Maybe the WARStructure can fire something off?

Hmmm, could be probably extended.
Or new PersistenceUnitStructure, but I dunno how would that play with
existing WARStructure --> PUS's deployment ~ WS's classpath entry.

[wolfc]

"alesj" wrote:
You could check all WEB-INF/lib jars for it
and create something useful.
Or create new structure - PersistenceUnitStructure.

I'm saying this w/o having any idea what the spec requires. ;-)

It's all in chapter 6 of EJB3 persistence, about 10 pages.

"alesj" wrote:
Hmmm, could be probably extended.
Or new PersistenceUnitStructure, but I dunno how would that play with
existing WARStructure --> PUS's deployment ~ WS's classpath entry.

Me neither. :-)

[alesj]

"wolfc" wrote:

Me neither. :-)

Try it. ;-)

[adrian.brock]

I don't understand why there is a long discussion.

It's clearly a bug. The WARStructure is adding WEB-INF/classes/META-INF
as a metadata location, but not the META-INF folders of the nested jars.

 // Create a context for this war file with WEB-INF as the location for metadata
 // Some wars also might have metadata in WEB-INF/classes/META-INF, e.g. persistence.xml
 context = createContext(structureContext, new String[]{"WEB-INF", "WEB-INF/classes/META-INF"});

[adrian.brock]

JIRA Issues:
https://jira.jboss.org/jira/browse/JBAS-5911
https://jira.jboss.org/jira/browse/JBAS-5912

[wolfc]

Keep in mind we currently don't want to accidentally deploy EJBs defined in such a jar. Would be nice if this is some boolean we can switch on at will.