If nested components need activation context parameters, the page
could always stick them on the Environmental Stack.
Engineering this further, you could have a service which is injected
into both the page and the component which stores it's state in a
ThreadLocal.
Steve.
On 24 October 2011 21:37, Barry Books <trs...@gmail.com> wrote:
> I would agree about activate/passivate in a component because there is
> no way to namespace the parameters so the component is pretty much
> tied to the page, but since the URL parameters are name/value pairs I
> can name things in such a way to avoid conflicts.
>
> My use case is a pagination component. I want to place the page number
> in the URL but this restriction means more code for no apparent
> reason. Now I need (and I loose the value converters)
>
> @BeginRender
> void init() {
> String page = request.getParameter(parm);
> currentPage = new Integer(page);
> }
>
>
> I suspect there are other use cases like this such as a search component.
>
> ---------------------------------------------------------------------
> 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
