openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Qin Feng" <>
Subject OpenJPA EntityManager.clear() should not implicitly invoke the flush operation - em.persist - em.clear - em.merge scenario doesn't work
Date Thu, 11 Sep 2008 23:28:52 GMT
After fix of openjpa-119, EntityManager.clear() now don't flush new object but only detach
But DetachManager still flush dirty object and assume detached objects are in clean state.

When the "new" object is merged back and transaction commit, because the object state lost
its original state PNEW, it will not be added to insert list and not flushed to DB. 

According to the EntityManager.clear() API, changes made to entities that have not been flushed
to the database will not be persisted. When they merges back to persistent context, they all
should kept there original state. 

I added the following test to org.apache.openjpa.persistence.simple.TestEntityManagerClear.

    public void testClearMerge() { 
        // Create EntityManager and Start a transaction (1) 

        // Insert a new object then clear persistent context 
        AllFieldTypes testObject1 = new AllFieldTypes(); 
        testObject1.setStringField("my test object1"); 
        //Object1 is not flushed to DB but only detached by clear(). 
        //expect the PCState is same as before detached, 
        //so it is PNew instead of PCLEAN and is add to insert list. 
        //Start a new transaction 
        // Attempt retrieve of Object1 from previous PC (should exist) 
        assertEquals(1, query("select x from AllFieldTypes x " 
            + "where x.stringField = 'my test object1'"). 
        // Rollback the transaction and close everything 

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message