I'd write a mixin that just changes the method from POST to GET on the form element. You might need to put in a different URL if Tapestry gets confused about the form URL being a GET. Then just attach that mixin to the form component. I've thought about this for searches but I just put @ActivationRequestParameter on the values for the form inputs. The only drawback is the extra redirect after the POST.
-- View this message in context: http://tapestry.1045711.n5.nabble.com/form-method-GET-tp5719423p5719433.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
