Eclipse Community Forums: EclipseLink » Persistence Units definitions are conflicting?

Home » Eclipse Projects » EclipseLink » Persistence Units definitions are conflicting?(Using two persistence units, one with annotation and on with orm.xml causes weird behaviour.)

Show: Today's Messages :: Show Polls :: Message Navigator

Persistence Units definitions are conflicting? [message #1849402]

Mon, 17 January 2022 23:56

Hans Pikkemaat

Messages: 9
Registered: January 2021

Junior Member

Hi,

I want to use one class and two JPA persistence units and as such to be able to store data in different tables (or even databases) and different definitions.

According to the JPA2.2 specification this should be possible but I experience weird behaviour. I'm using payara which uses eclipselink.

For a complete description and a reproducer see this github project:

https://github.com/thehpi/jpa-issue

I hope someone can help me.

Report message to a moderator

Re: Persistence Units definitions are conflicting? [message #1849667 is a reply to message #1849402]

Fri, 28 January 2022 16:27

Hans Pikkemaat

Messages: 9
Registered: January 2021

Junior Member

The issue here is weaving. Weaving is done on the one model class but the resulting class depends on persistence.xml/orm.xml.

So having one model class and two persistence.xml/orm.xml definitions will not work.

For more info see here https://stackoverflow.com/questions/70748822/jpa-persistence-unit-definitions-are-conflicting/70896886#70896886

Report message to a moderator

Previous Topic:	duplicate persistence classes in classpath
Next Topic:	Downloading EclipseLink5.2.5 -> EclispeLink2.3.3 gives empty zip error

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Thu Dec 07 00:52:30 GMT 2023

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter