This content has been marked as final.
Show 4 replies
-
1. Re: TransactionalSeamPhaseListener
christian.bauer May 2, 2007 5:11 PM (in response to xmas_spirit)1) Subclass and customize
2) You can't (that is good, there is no overhead if no transactional resources are used)
3) Committing after INVOKE APPLICATION and opening a second transaction in RENDER RESPONSE (which usually only reads data) keeps locks in the database, created from inserts, updates, and deletes during INVOKE APPLICATION, as short as possible -
2. Re: TransactionalSeamPhaseListener
xmas_spirit May 2, 2007 5:38 PM (in response to xmas_spirit)3/ ok, i know why do you commit the first one, but do you need a transaction to read data?
-
3. Re: TransactionalSeamPhaseListener
christian.bauer May 2, 2007 5:44 PM (in response to xmas_spirit)Of course, why wouldn't you?
http://www.hibernate.org/Documentation/NonTransactionalDataAccessAndTheAutoCommitMode -
4. Re: TransactionalSeamPhaseListener
xmas_spirit May 2, 2007 6:25 PM (in response to xmas_spirit)ok, tnx... but one more:
2/ what if i have to call a session bean method annotated with @TransactionAttribute(TransactionAttributeType.NOT_SUPPORTED)