Splitting entities amongst several JARs is definitely supported by JPA 2, you need to use
the <jar-file> element in persistence.xml (or to a lesser extend <class>).
Merging several persistence.xml and considering them one is not a concept that makes sense
in the JPA 2 spec. Conceptually that means a lot of metadata duplication that can and will
conflict.
The exception you see comes from the fact that your "merging" does not
"unduplicate" jar file urls and it's associated root url.
Emmanuel
On 3 févr. 2010, at 17:43, Bouiaw wrote:
Hi,
I would like to warn you about a blocking (from my point of view)
issue in Hibernate 3.5 (JIRA issue :
http://opensource.atlassian.com/projects/hibernate/browse/HHH-4864).
Dispatching entities is not supported out of the box by Hibernate/JPA,
but with a small tweak commonly used
(
http://ancientprogramming.blogspot.com/2007/05/multiple-persistencexml-fi...)
it is possible to acheive this.
This worked with previous version of Hibernate, but not anymore in
Hibernate 3.5 betas.
Even if this is not specified in JPA, this is mandatory for a lot of
developer to do modular applications (each module (JAR) provide its
own DAO, business and model layer).
I hope you will be able to fix HHH-4864, because this is a blocking
point for a lot of developers.
Thanks in advance for your feedback,
Bouiaw
_______________________________________________
hibernate-dev mailing list
hibernate-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev