Interesting idea is to use a message broker to create complex commit/rollback rules between UpdateManager instances on separated machines (runtimes) for dealing with managed Java applications. John
2010/5/3 JayaPrakash <[email protected]> > > Hi Michael, > > Thanks for your reply. I already have that configuration in place, > but the problem is that, since I am using the @ElementDependent for orphan > deletion, to honor the SQL order while delete, the OpenJPA is updating the > child table foreignkey values to null, since my DB does not allow nulls in > to foreignkey columns, i get an error. > > So, I was wondering if there is a way that I can force a particular object > to be inserted/updated first before all the other objects in the Tree. > Since, the object that is at the top most level needs to be inserted first > because of some requirement that we have. > > Thanks, > JP > -- > View this message in context: > http://openjpa.208410.n2.nabble.com/Forcing-an-Object-to-be-always-inserted-updated-first-during-persist-merge-tp4990960p4999545.html > Sent from the OpenJPA Users mailing list archive at Nabble.com. >
