Excellent!
But what let's say there's a 2nd link transformer, what happens to the
PageRenderRequestParameters that the two transformers return? Would the second
one just inject an EventContext
@Inject
private EventContext eventContext;
and use it to generate the new EventContext? As well, would the 2nd transformer
get an adjusted path in the Request ... (or how else would I do additional path
munging?)
public PageRenderRequestParameters decodePageRenderRequest(Request request)
{
Thanks!
Jochen
On Jan 31, 2012, at 9:42 AM, Thiago H. de Paula Figueiredo wrote:
> On Tue, 31 Jan 2012 15:35:13 -0200, Jochen Frey <joc...@jochenfrey.com> wrote:
>
>
>> Let's say there's a page /SomeAccount/profile/SomeOtherVar, where
>> "SomeOtherVar" is supposed to go into the activation context as well ... how
>> would I handle that? Do I have the shot of augmenting the activation
>> context somewhere on a per-page basis, or do I need to handle all possible
>> Activate Context variations in the LinkTransformer? In other words, is
>> there some chain where more processing of the URL is done?
>
> Don't forget that you can have more than one LinkTransformer. They're
> chained, so you need to ensure they're contributed in the right order.
>
> --
> Thiago H. de Paula Figueiredo
> Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, and
> instructor
> Owner, Ars Machina Tecnologia da Informação Ltda.
> http://www.arsmachina.com.br
---
joc...@jochenfrey.com
+1.415.366.0450
@jochen_frey
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
