Eclipse Community Forums: EclipseLink » 2.0.0: where did the commit go?

Help

Home

Home » Eclipse Projects » EclipseLink » 2.0.0: where did the commit go?

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

2.0.0: where did the commit go? [message #507216]

Tue, 12 January 2010 14:20

Tom Eugelink

Messages: 817
Registered: July 2009

Senior Member

When I execute a native query inside an Eclipse event, the commit is not executed.

This is the testcode:

public static void main(String[] args)
{
// EntityManager
EntityManagerFactory lEntityManagerFactory = ...
EntityManager lEntityManager = lEntityManagerFactory.createEntityManager();

// bind eclipse events to Batchtransferline
JpaEntityManager lJpaEntityManager = (JpaEntityManager)lEntityManager;
EclipselinkDescriptorEventListenerRouter lEclipselinkDescriptorEventListenerRouter = new EclipselinkDescriptorEventListenerRouter();
lJpaEntityManager.getSession().getClassDescriptor(Batchtrans ferline.class).getEventManager().addListener( lEclipselinkDescriptorEventListenerRouter );

// delete batchtransfer
try
{
Batchtransfer lBatchtransfer = lEntityManager.find(Batchtransfer.class, BigInteger.valueOf(15));
lEntityManager.getTransaction().begin();
Batchtransfer lMergedEntity = lEntityManager.merge(lBatchtransfer);
lEntityManager.remove( lMergedEntity ); // remove the merged entity
lEntityManager.getTransaction().commit();
}
catch (Throwable t)
{
t.printStackTrace(System.out);
System.out.println(">>> " + t.getMessage());
}

// close shop
lEntityManager.close();
lEntityManagerFactory.close();
}

This EclipselinkDescriptorEventListenerRouter class is just for redirecting the event to the entity.
I make sure all my entities have implemented EclipselinkEntityEventListener, so the it can do:

...
// delete
public void preDelete(DescriptorEvent descriptorEvent)
{
((EclipselinkEntityEventListener)descriptorEvent.getObject() ).preDelete();
}
public void aboutToDelete(DescriptorEvent descriptorEvent)
{
((EclipselinkEntityEventListener)descriptorEvent.getObject() ).aboutToDelete();
}
public void postDelete(DescriptorEvent descriptorEvent)
{
((EclipselinkEntityEventListener)descriptorEvent.getObject() ).postDelete();
}
...

The Batchtransferline then has:

@Override
public void postDelete()
{
Query lQuery = EntityManagerFinder.find().createNativeQuery("select sum(amount) from batchcount where to_amount_batchtransferlinenr=19");
lQuery.setFlushMode(FlushModeType.COMMIT); // make sure the query does not force the entity to be flushed to the DB
BigInteger lCurrentAmount = new BigInteger( EclipselinkUtil.getSingleResultOrDefault(lQuery, "0").toString() );
}

If the lines in the event method are commented out, I get:
...
[C1173553]: setAutoCommit( false )
...
[C1173553]: executeUpdate: DELETE FROM batchtransfer WHERE ((batchtransfernr = ?) AND (lazylock = ?))
[C1173553]: commit()
... stack trace
>>> Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.0.0.v20091127-r5931): org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: java.sql.SQLException: Key value for constraint (informix.u208_344) is still being referenced.
Error Code: -692
[EL Info]: 2010-01-12 15:08:41.206--ServerSession(30284778)--reinders_url= jdbc:reinders:com.informix.jdbc.IfxDriver#jdbc:informix-sqli ://toeu_reinders:9088/reinders:INFORMIXSERVER=ol_ids_1150_1;DB_LOCALE=en_us.utf8_user=user logout successful

This is correct! The record cannot be deleted, because there are references. This is what is supposed to be solved in the event logic.
Now if the three lines in the event method are active, I get:
...
[C14626104]: setAutoCommit( false )
...
[C14626104]: executeUpdate: DELETE FROM batchtransfer WHERE ((batchtransfernr = ?) AND (lazylock = ?))
[EL Info]: 2010-01-12 15:08:41.206--ServerSession(30284778)--reinders_url= jdbc:reinders:com.informix.jdbc.IfxDriver#jdbc:informix-sqli ://toeu_reinders:9088/reinders:INFORMIXSERVER=ol_ids_1150_1;DB_LOCALE=en_us.utf8_user=user logout successful

The delete statement is the last entry in the log; no close, no commit, no rollback... No exception! Because I still cannot delete the record!

How can only adding the native query cause this?

Tom

Breadcrumbs

Sign up to our Newsletter