Alejandro, you mentioned @ActivationRequestParameter which I was confusing with @PageActivationContext which you can only have one of. I think I can get it to work with multiple @ActivationRequestParameter for each filter field.
Thanks. I'm still of the opinion that tapestry should support <form method="GET" /> as it's a valid use-case. Google uses a "GET" for search. -- View this message in context: http://tapestry.1045711.n5.nabble.com/form-method-GET-tp5719423p5719443.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