This is an issue that has appeared many times on this list, you should search
for old posts on this, the gist of it is these examples were provided before
newer functionality (such as ComponentClassResolver and ComponentSource etc..)
were added to Tapestry that can handle this problem better.
I created the ComponentRequestHandler service (a pipeline, with
filters) for this purpose; to make a single logical place to put
filters for both page render requests and component event requests.
public interface ComponentRequestHandler
{
/**
* Handler for a component action request whic
Thiago H. de Paula Figueiredo schrieb:
Em Tue, 25 Aug 2009 11:33:18 -0300, Sebastian Hennebrueder
escreveu:
But it is an internal service which are from my understanding
discouraged to use.
ComponentEventLinkEncoder isn't internal, as it's in the
org.apache.tapestry5.services package. Only
Em Tue, 25 Aug 2009 11:33:18 -0300, Sebastian Hennebrueder
escreveu:
But it is an internal service which are from my understanding
discouraged to use.
ComponentEventLinkEncoder isn't internal, as it's in the
org.apache.tapestry5.services package. Only classes and interfaces in
packages
Thiago H. de Paula Figueiredo schrieb:
Em Tue, 25 Aug 2009 11:25:42 -0300, Sebastian HennebrŸüder
escreveu:
Hello,
Hi!
A correct implementation needs to implement the page name extraction as
done in ComponentEventLinkEncoderImpl.decodeComponentEventRequest and as
in the decodePageRenderRe
Em Tue, 25 Aug 2009 11:25:42 -0300, Sebastian HennebrŸüder
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 d
