This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
3. On page 556 6. A bean wants the client to get an application exception, but the bean still wants the transaction to commit. What should the bean do?
Are they looking for answer, do not call setRollbackOnly and let the exception propogate to container and in turn client as is? I can not think of anything that we can do to ensure that transaction commits.
[ March 21, 2005: Message edited by: Gemini Moses ] [ March 21, 2005: Message edited by: Gemini Moses ]
"When an instance attempts to start a transaction using the begin() method of the javax.transaction.UserTransaction interface while the instance has not committed the previous transaction, the Container must throw the javax.transaction.NotSupportedException in the begin() method. "