Hi Nick! As I said request-serializing was discarded by our department for some reasons. IMHO should Tapestry address this issue, and I wanted to ask wheter there is a version which does not have this problem anymore.
I looked at the source as well, and must say I do not understand why the exception is thrown at all. Maybe someone can explain. Thanks Reinhold -----Original Message----- From: Nick Westgate [mailto:[EMAIL PROTECTED] Sent: Donnerstag, 25. Jänner 2007 11:49 To: Tapestry users Subject: Re: Page Recorder Locked in Tapestry 3.0 Hi Reinhold. The solution is to implement a request filter that serializes requests with (for example) code from this article: http://www.onjava.com/pub/a/onjava/2004/03/24/loadcontrol.html Cheers, Nick. Reinhold Gruber wrote: > Hi! > > > > Is there a Tapestry Version 3.0.x which solves the "page recorder locked > after commit" issue for concurrent requests of the same user? > > > > If not: > > Using JavaScript to disable form buttons after the first submission or > serializing user-requests are no option for our applications. > > I read somewhere about a custom engine which ignores this exception but > did not found an example. > > > > Thanks, > > Reinhold > > > > --------------------------------------------------------------------- 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]
