users@glassfish.java.net

Re: Try to understand how works Toplink

From: <glassfish_at_javadesktop.org>
Date: Mon, 14 Apr 2008 07:48:05 PDT

Hello,

Not sure of the answer to 1, but what you are seeing are what the JPA provider (TopLink Essentials) can tell you. In this case, its only handle to the transaction is to the before and after completion events on the transaction, so that is what its logging can tell you. The container logging will likely tell you about the actual transaction.

2) MethodB is executing a query, which is probably causing a flush of all changes upto that point, due to the default FlushModeType.AUTO. You can change the flushmode using the setFlushMode api if this isn't what you want.

Best Regards,
Chris
[Message sent by forum member 'chris_delahunt' (chris_delahunt)]

http://forums.java.net/jive/thread.jspa?messageID=269056