Yes, I'm using spring.transaction.TransactionInterceptor on my DAO. I am doing getTransactionUtils().setRollbackOnly() outside my DAO in the same way as you are doing in tapernate-example.
Here is a stack trace. I will get back to you with more logging. http://pastebin.com/734105 in AbstractPlatformTransactionManager.commit(...) : if (!shouldCommitOnGlobalRollbackOnly() && defStatus.isGlobalRollbackOnly()) { ... processRollback(defStatus); throw new UnexpectedRollbackException( "Transaction has been rolled back because it has been marked as rollback-only"); } Thanks Marcus On 5/24/06, James Carman <[EMAIL PROTECTED]> wrote:
I will take a look at it. Are you using a transaction interceptor? Can you paste more of your stack trace? Can you turn up logging so we can see exactly what's going on? -----Original Message----- From: Marcus Matèrn [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 23, 2006 6:10 PM To: Tapestry users Subject: Tapernate - Rollback problem I'm trying to use setRollBackOnly() in tapernates TransactionUtils which results in: UnexpectedRollbackException: Transaction has been rolled back because it has been marked as rollback-only when the commit runs in: org.springframework.transaction.support.AbstractPlatformTransactionManager.c ommit(AbstractPlatformTransactionManager) I am getting the same problem when running tapernate-example. Does someone (James?) know a solution to my problem? Marcus --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]