No problem! Just to be clear about why your situation is working now, I removed the transaction interceptor from the persistence strategies and the "squeezer." With transaction-per-request turned on, these features work just fine. You can disable transaction-per-request, but I would imagine that the majority of Tapernate users are using it. Again, Tapernate is a "work in progress", so I'm trying to figure out the best way to get around this issue. I really don't like the fact that the Spring transaction interceptor throws an exception. I think I can let it just go by without rolling back the transaction and without throwing an exception. I'll try to figure that out.
-----Original Message----- From: Massimo Lusetti [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 24, 2006 6:08 AM To: Tapestry users Subject: Re: New version of Tapernate... On 5/24/06, James Carman <[EMAIL PROTECTED]> wrote: > First of all, no I have not moved Tapernate as of yet. But, I wanted to let > you know about a few new features... Thanks James! -- Massimo http://meridio.blogspot.com --------------------------------------------------------------------- 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]
