On Fri, 24 Aug 2012 16:02:08 -0300, Michael Prescott
<michael.r.presc...@gmail.com> wrote:
Okay, it works correctly if I specify the following constraints:
after:Asset
after:ComponentEvent
before:PageRender
(The semantics of this mystify me, it seems redundant. Given the order
on the graphic Joakim sent, I'd have thought that after:ComponentEvent or
before:PageRender would be sufficient, but apparently not. If anyone
has a fuller understanding, I'd love to hear it.)
For any two contributions that don't have any sorting constraints related
to each other, directly or indirectly, the ordering of their additions
(including the processing of the module classes in which they are located,
which isn't deterministic) can cause different orderings in the end.
If you add your contribution with after:ComponentEvent, it doesn't mean it
will be place immediately after ComponentEvent, but that, in the end, your
contribution will be guaranteed to be placed in some place after
ComponentEvent. In other words, ComponentEvent will be invoked before your
contribution.
Q. How do you tell whether the request corresponds to a vanilla request
to render a page?
PageRenderRequestParameters decode =
componentEventLinkEncoder.decodePageRenderRequest(request);
plus checking whether the matched page really exists using ComponentSource.
(or)
Q. How do you tell which page a component event corresponds to?
ComponentEventRequestParameters decoded =
componentEventLinkEncoder.decodeComponentEventRequest(request);
String containingPageName = decoded.getActivePageName();
--
Thiago H. de Paula Figueiredo
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
