I suspect you are using @ActivationRequestParameter annotatations and that
is the source of your "sticky" query parameters.
It may be a bug that you explicitly supply an empt parameters map to the
PageLink and it still adds the ARP in, but that is likely a feature.
To accomplish what you want, you may need to set the ARP fields to null
inside beginRender().
On Wed, May 8, 2013 at 6:02 AM, Barry Books <trs...@gmail.com> wrote:
> I've got a menu item generated from a database with a pagelink like this
>
> <t:pagelink page="prop:drop.page" context="dropContext"
> style="${drop.style}"
> >${drop.label}</t:pagelink>
>
>
> I've added a search function to one of the linked pages that adds
> parameters to the URL with
>
>
> <t:pagelink ... parameters="search">Page</t:pagelink>
>
>
> I'd like to make the menu item clear the search so I tried this:
>
>
> <t:pagelink page="prop:drop.page" context="dropContext" style="${drop
> .style}" parameters="{}">${drop.label}</t:pagelink>
>
>
> but it does not work. It seems Tapestry is clever enough to always add my
> search criteria to the parameter map. This would be easy enough to fix if
> my menu was not driven from a database but I don't see an easy to make my
> generic menu know how to fix this.
>
>
> It would seem useful to be able to say <t:pagelink ...
> parameters="null">Page</t:pagelink> but parameters cannot be set to null.
>
>
> Any suggestions?
>
--
Howard M. Lewis Ship
Creator of Apache Tapestry
The source for Tapestry training, mentoring and support. Contact me to
learn how I can get you up and productive in Tapestry fast!
(971) 678-5210
http://howardlewisship.com
