This discussion is super relevant for multi module project development in IDE's too.
I've followed up - I hope emmanuel do too since this one actually is one of my
biggest issues I have when it comes to "autoscanning".
----- "Bouiaw" <bouiaw(a)gmail.com> wrote:
Thanks for your answer.
I made some tests but I think there is no way to acheive this my
(common) need without tweaking with merging in one PU.
I don't want to SPAM the dev list so I created a thread on the
Hibernate forum with my feedback :
On Thu, Feb 4, 2010 at 9:06 AM, Emmanuel Bernard
> 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.
> On 3 févr. 2010, at 17:43, Bouiaw wrote:
>> I would like to warn you about a blocking (from my point of view)
>> issue in Hibernate 3.5 (JIRA issue :
>> Dispatching entities is not supported out of the box by
>> but with a small tweak commonly used
>> 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
>> developer to do modular applications (each module (JAR) provide
>> own DAO, business and model layer).
>> I hope you will be able to fix HHH-4864, because this is a
>> point for a lot of developers.
>> Thanks in advance for your feedback,
>> hibernate-dev mailing list
hibernate-dev mailing list