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
