I agree with you, merging persistence.xml is ugly.
But more than a specific IDE issue, I think this is more a general
"dynamically discover Entites in != classloaders" related issue.
I have made some prototypes and my conclusion is that JPA is not build
for my use case, even if it is a real need a
Guys,
The approach consisting of merging persistence.xml files is super broken.
Period. It's a hack that happens to work for some version(s) of Hibernate but
surely fails on other providers and is totally against the spirit and the word
of the spec.
The only decent approach I can think of is fo
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".
/max
- "Bouiaw" wrote:
> Thanks for your answer.
>
> I made some tes
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 :
https://forum.hibernate.org/viewtopic.php?f=1&t=1002467
Splitting entities amongst several JARs is definitely supported by JPA 2, you
need to use the element in persistence.xml (or to a lesser extend
).
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 metad
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://ancie
