Hi,I can't tell from your description what might be going wrong, but there is one clue. You ask if all entities should be persisted in one transaction. Not necessarily. But if you have several transactions, it's possible that you are using detached instances and the problem might be that if you assign an instance to a field of a detached instance and then commit the transaction, nothing happens!
You need to make sure you merge all detached instances or nothing is supposed to happen.
Can you attach a test case? Craig On Dec 4, 2007, at 2:24 PM, JuneG wrote:
we have an entity has one-to-many relationship to several other entities, we use EntityManager's persist method to do cascade persist. Occasionally one of the entities in this graph did not get persisted while all the others were persisted successfully, and there is no exception raised why the entitydid not get persisted. If we re run the process all entities will bepersisted successfully. any idea why this is happening? is that all entitiesshould be persisted in one transaction? we are using weblogic 10 any input will be appreciated. thanks!! --View this message in context: http://www.nabble.com/Casade-Persist- tf4946103.html#a14160955Sent from the OpenJPA Users mailing list archive at Nabble.com.
Craig Russell Architect, Sun Java Enterprise System http://java.sun.com/products/jdo 408 276-5638 mailto:[EMAIL PROTECTED] P.S. A good JDO? O, Gasp!
smime.p7s
Description: S/MIME cryptographic signature
