Yes OpenJPA will occasionally flush when/if it is deemed necessary. One
example that comes to mind is the openjpa.FlushBeforeQueries property[1]...
I'm sure there are others, but I can't come up with all of the different
ones.
The thing that concerns me is that you have Entities that aren't really
Hi Rick,
Thanks for your reply!
Well actually we do not have any "unwanted flush calls" but we are scared
that they might happen ; )
But let's take about the details:
We try to upgrade an old JEE application (with an custom developed
PersistenceFramework) to JPA.
Because of effort and QA r
Nothing immediately comes to my mind. Perhaps a better explanation of what
you are trying to do will expose some other solution. One question though,
what is currently driving the unwanted flush() calls?
Thanks,
Rick
On Mon, Aug 11, 2014 at 1:24 PM, Christoph Weiss wrote:
> Dear Community,
>
>
Dear Community,
We are running OpenJPa with "container managed" EntityManagers (using
WebSphere Application Server).
Because of technical reasons we want to explicitly control when the
EntityManager executes the flush.
First I thought that the parameter "FlushMode" could be a solution, but
