I've tried that one, couldn't make it work. As far as I can remember, there were issues with putting the HttpServletRequest into the session, because it isn't serializable. Same thing with java.lang.Object.
Anyone with a working version of this? http://www.onjava.com/onjava/2004/03/24/examples/RequestControlFilter.java Inge On 3/14/06, Nick Westgate <[EMAIL PROTECTED]> wrote: > > Hi Christian. > > This may not be relevant - but just in case - there was an > issue with Tapestry 3 to do with double clicking submits. > > I'm not using T4 yet and things may have changed, but read this: > > http://article.gmane.org/gmane.comp.java.tapestry.user/19128/match=locked+filter > > Cheers, > Nick. > > > Christian Mittendorf wrote: > > Thanks for the hint. I will give your approach a try tomorrow! > > > > Christian > > > > > > Am 13.03.2006 um 18:20 schrieb Inge Solvoll: > > > >> See the token-discussion in another recent thread, which > discusses this > >> issue. (double submit) > >> > >> On 3/13/06, Bryan Lewis <[EMAIL PROTECTED]> wrote: > >> > >>> > >>> Look in your page spec or template for a binding like map.areaCode > . It > >>> sounds like you have a hashmap with an areaCode key, and the > map isn't > >>> declared persistent. Or pehaps it's being nullified in the first > >>> submit. When the second submit comes along, the page is trying to > >>> store > >>> the areaCode in a null map. > >>> > >>> Christian Mittendorf wrote: > >>> > >>>> Hello! > >>>> > >>>> Using a double-click for selecting buttons is - as far as I can tell > >>>> from my observations - a common "mistake" of computer beginners. I > >>>> know a number of new computer users, that apply this pattern - which > >>>> they know from the desktop for opening files - to navigating web > >>>> pages and submitting web forms. > >>>> > >>>> We are tracking the exceptions from our live applications and there > >>>> is one exception, that we really couldn't either recreate with our > >>>> test environment nor could we explain it. Probably we have found a > >>>> hint now... > >>>> > >>>> The error is always (better very often) a null pointer > exception with > >>>> an error message like this: > >>>> > >>>> target is null for setProperty(null, "areaCode", 040) > >>>> > >>>> While developing a new application I accidentally did a fast double > >>>> click on a button and I got the error message shown above. I > was also > >>>> able to reproduce this exception, although it wasn't always the same > >>>> property that did cause the exception. > >>>> > >>>> Has anybody else experienced something similar? What is the > cause for > >>>> this exception? I assume that it must have something to do with the > >>>> rewind cycle. Any ideas for my next steps to hunt down this > "bug" are > >>>> appreciated ;-) > >>>> > >>>> Christian > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
