Eclipse Community Forums: EclipseLink » right way to maintain bi-directional relationships

Help

Home

Home » Eclipse Projects » EclipseLink » right way to maintain bi-directional relationships

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

right way to maintain bi-directional relationships [message #1748941]

Wed, 30 November 2016 09:56

stefano grima

Messages: 2
Registered: August 2015

Junior Member

Hi Team,

I need to know how to maintain bidirectional manyToOne and OneToOne in the right way , beacause i have some problem while delete or update entities
in my application .

Environment

Payara Version: 4.1.1.163
- Edition: Full
- JDK Version: 8 - Oracle
- Operating System: Linux

Framework
- jsf + primefaces
- eclipselink

Report message to a moderator

Re: right way to maintain bi-directional relationships [message #1749092 is a reply to message #1748941]

Thu, 01 December 2016 18:07

Chris Delahunt

Messages: 1389
Registered: July 2009

Senior Member

Not sure I understand. When you make a change to one side, you must make the corresponding change to the other side and ensure both changes are picked up by the context -either by modifying managed entities or merging both changed detached instances back into the context. What exactly are you doing?

Report message to a moderator

Re: right way to maintain bi-directional relationships [message #1749401 is a reply to message #1748941]

Tue, 06 December 2016 09:49

stefano grima

Messages: 2
Registered: August 2015

Junior Member

My question is : what is the best solution to maintain the relation ?
In my applications the users can change the associations through the interaction with the view (JSF framework) . I ensure the relation's maintenance
in the stateless EJB responsible for the management of transactions in the persistence context .
The hardest part is the update method because i change the state of three entities for each change of association :
1 - The relation owner entity
2 - The old inverse entity ( remove operation on the oneToMany list )
3 - The new inverse entity ( add operation on the oneToMany list )

Report message to a moderator

Previous Topic:	How to get Eclipselink to fire JSR303 constraints in mapped super class?
Next Topic:	EclipseLink - @OneToOne mapping does not update MongoDB(NoSQL)

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Fri Apr 26 18:11:08 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter