The solution i used is to create the inderiction key at the very end of activation encoding in ContextValueEncoder. I mean just after toClient() call, i get the resulting string and transform it. Then before calling delegated toValue i retrieve the direct reference from the indirection key provided as a parameter to the toValue method.
I see this drawback to my approach, it's that i do not have access to many informations about which parameter is decoded, thus disabling for a specific parameter will be hard to implement, i can handle disabling per page. On the other side, this entry point is satisfying for other reason, i manipulate only String no need to define multiple ContextValueEncoders. I have to find a solution between yours (which is more flexible regarding the type of target value) and mine that is fairly simple to implement. Regards, Christophe. 2010/2/3 Thiago H. de Paula Figueiredo <thiag...@gmail.com> > On Wed, 03 Feb 2010 07:09:54 -0200, Peter Stavrinides < > p.stavrini...@albourne.com> wrote: > > Interesting solution! >> > > ActivationContextEncoder aand friends are part of the Tapestry CRUD > package. If you provide the object access logic, the package invokes it > automatically for you. > > > -- > Thiago H. de Paula Figueiredo > Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, > and instructor > Owner, software architect and developer, Ars Machina Tecnologia da > Informação Ltda. > http://www.arsmachina.com.br > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > >
