We are having an issue dealing with an entity bean backed JSF page where we are updating the entity via an AJAX call. At the end of the AJAX call the changes are flushed and committed to the database.
With the realization that this is the default behavior of Seam and after searching the forums I have attempted this:
1) Start a conversation with flush-mode set to 'manual'. We are using the pages.xml file to start / stop our conversations as opposed to annotations.
2) Find the entity. The entity contains a @OneToMany with one of the the many side entities being updated via the AJAX call.
3) Manually flush() when save() is called.
Unfortunately, even with flush-mode set to manual for the conversation, step 2 in the process is still flushing and committing the changes to the DB.
The debug.seam page does show our long running conversation's persistence context's flush mode set to MANUAL.
We are using:
JBoss 4.2.0 GA
We figured this out. We were using the standard EJB3 persistence context instead of the Seam managed one.