Hi Lance
Can you tell us more about what are you trying to achieve with using
the GET method?
If you are after bookmarkability and persistence after refresh then I
think that @ActivationRequestParameter is a good option, as Barry
said.
My approach is to do the filtering during the setupRender and I don't
use the same property for the request parameter and the form field.
Something like this:
@ActivationRequestParameter
private String q;
@Property
private String qField;
@SetupRender
void setup()
{
source = new HibernateGridDataSource(session, beanType)
{
protected void applyAdditionalConstraints(Criteria crit)
{
if (q != null && !q.isEmpty()) {
// filter your criteria in here...
}
}
};
}
@OnEvent(EventConstants.SUCCESS)
void search()
{
q = qField;
}
I hope it helps.
Cheers.
Alejandro.
On Wed, Jan 23, 2013 at 3:00 AM, trsvax <trs...@gmail.com> wrote:
> 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
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
