Thanks, that description cleared that up. Let's say you have a conversation with several methods (one method called per request) and I use FlushMode.COMMIT/AUTO. If the first few requests in the conversation access a NEVER or NOT_SUPPORTED action method, and the next request accesses a REQUIRES (or similar) action method, would the persistence context be flushed when that REQUIRES method successfully returns?
Or would changes be flushed after every request because of the fact that there's always a transaction? anonymous wrote : use two transactions per request; the first spans the beginning of the update model values phase until the end of the invoke application phase; the second spans the render response phase How do the transactions from the quote above relate to the transactions specified by the transaction attributes? If somebody could please lay this all out for me that'd be wonderful...I've been reading the Seam and Hibernate sections on transactions, but now I just need to ask a human... View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4006062#4006062 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4006062 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
