Well, actually what I need is - dedicated activation context for a component, something like current onActivate() for pages
- passing request parameters to PageLink, like <t:PageLink requestparameters="linkRequestParamaters" context="linkContext" > I'm implementing a pager that generates "forward" - "backward" links without EventLinks to avoid excessive http requests. The first item would help me to avoid reflection. And the second would help me to code optional "pageNum" parameter using the standard request parameter notation "?pageNum=3", not my own odd format "/pageNum-3:anotherParameter-ENUM_PARAMATER_VALUE" that I implemented by contributing ParamaterMap ValueEncoder as was advised on this list for optional parameters. On Sat, Jun 13, 2009 at 1:58 AM, Thiago H. de Paula Figueiredo<thiag...@gmail.com> wrote: > Em Fri, 12 Jun 2009 18:54:59 -0300, Sergey Didenko > <sergey.dide...@gmail.com> escreveu: > >> And call onPassivate() through reflection, right? > > Yes. But we can try to find a bfile a JIRA for a better way of getting that > info without using reflection. > >> I missed this case because did not expect my "live" page to extend >> interface Component that is returned from componentResources.getPage() > > The magic of Tapestry modifying our component classes in runtime . . . long > live Javassist! :) > >> Thanks for your answers! > > It's a pleasure to help. :) > > -- > Thiago H. de Paula Figueiredo > Independent Java consultant, developer, and instructor > http://www.arsmachina.com.br/thiago > > --------------------------------------------------------------------- > 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
