I did some testing and while I can see a reason to support GET, I think the way forms currently work make @ActivationRequestParamater along with the redirect a better choice because Tapestry uses a hidden field to map the form data to the Java parameters and I don't think you want that in the URL. The only real drawback to POST this is the 302 redirect but also happens on event links. If you don't care about bookmarks you can use a zone which eleminates the need for the redirect.
That's the way i've implemented bookmarkable no session searches and it seems easy enough. In your case having a filter object complicates things a bit because you have to move data in a out of the filter object but you could create a ValueEncoder for that. -- View this message in context: http://tapestry.1045711.n5.nabble.com/form-method-GET-tp5719423p5719461.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
