Em Tue, 25 Aug 2009 11:25:42 -0300, Sebastian HennebrŸüder
<hennebrue...@laliluna.de> escreveu:
Hello,
Hi!
A correct implementation needs to implement the page name extraction as
done in ComponentEventLinkEncoderImpl.decodeComponentEventRequest and as
in the decodePageRenderRequest method of the same class.
Why don't a correct implementation just inject ComponentEventLinkEncoder
and use its methods? That's exactly what I do.
The following documentation is affected
http://wiki.apache.org/tapestry/Tapestry5HowToCreateADispatcher
http://wiki.apache.org/tapestry/Tapestry5HowToCreateADispatcher2
http://wiki.apache.org/tapestry/Tapestry5HowToControlAccess
These examples were written before ComponentEventLinkEncoder existed, so
everyone is invited to update the wiki pages. :)
Can someone please validate this? I think we need to provide either a
service to decode page names or at least show how to do it properly.
ComponentEventLinkEncoder already does that.
--
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
