The likely cause of this observation is: the query determined that current cache holds dirty objects that can affect the result of the query. Hence it flushed them and a post update was notified.
Try specifying openjpa.IgnoreCache=true ----- Pinaki Poddar Chair, Apache OpenJPA Project -- View this message in context: http://openjpa.208410.n2.nabble.com/Lifecycle-listener-invoked-on-Query-tp7329975p7330296.html Sent from the OpenJPA Users mailing list archive at Nabble.com.
