Hi, Thiago! Thanks for your reply. Is there a way to validate the t:formdata parameter please? Can I detect whether this parameter contains some meaningful value or not?
Best wishes Jarda > On May25, 2016, at 16:50, Thiago H de Paula Figueiredo <thiag...@gmail.com> > wrote: > > On Wed, 25 May 2016 08:48:17 -0300, Jaroslav Ciml <jaroslav.c...@jpower8.cz> > wrote: > >> Hi Barry, > > Hello, Jaroslav! > >> This pattern (form data groupped in DTO, simple initialization for POST >> requests in prepare for submit handler, more complex initialization for GET >> requests in prepare for render handler) is used about hundred times in our >> app but it produces this rare exception just in case of this form. >> >> I wonder, how can such error occur anyway. I can even hardly think of some >> hypothesis that would explain such behavior. >> >> Is it possible, that the parameter t:formdata is malformed in the POST >> request and "prepare for render" event is not triggered? However, I am in >> doubt whether this hypothesis makes sense. > > Actually, it makes a lot of sense. The actions to be taken in a form > submission are put into objects, serialized and put into t:formdata. So, if > t:formdata is malformed, you shouldn't expect anything happening correctly. > >> I have reproduced the issue in a very strange way. I have filled the form in >> the browser and submitted but I have also manually modified the POST request >> parameters before sending it to the server (via Firefox plugin Tamper Data). >> I have replaced the value of t:formdata (I know the parameter values of the >> request that caused the exception in production environment as our app >> reports exceptions via email in such case) and I have also removed the value >> of the parameter t:submit. > > > -- > Thiago H. de Paula Figueiredo > Tapestry, Java and Hibernate consultant and developer > http://machina.com.br > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
