Ok, I see. You want one of your activation methods to be called: either the
one with numeric context or the one with string context. As Thiago
suggested, just create an appropriate event context object and pass it.
BTW this can be implemented without the URL rewriting as well. Just provide
an acti
Hi,
It's quite possibly I'm missing something about the functionality of Tapestry
or the correct implementation for our problem.
I'm involved in a project where we're porting an existing application to a
Tapestry based app. The application has been written to respond to several URL
patterns wh
Hi,
somehow your description doesn't make sense to me. You are rewriting the
incoming URLs like //page/123 to //page?id=123. Why actually? The
incoming request path is a valid page rendering URL. It requests Page with
activation context 123 to be rendered. Why do you want to transform the
activati
Thanks Tiago,
I did see that Contenxt type before but didn't look into it since it's in the
internal package. I'll look into using ArrayEventContext.
Are there plans to make a public API to the EventContext manipulation or to
maybe create a new set of API for that purpose?
I would imagine tha
On Tue, 07 Sep 2010 22:30:58 -0300, Marek Stanisław Wawrzyczny
wrote:
Hi,
Hi!
Yes, I'm working with incoming links. The code I have so far:
I guess you're missing some ready-to-use, non internal EventContext
implementation. All them in Tapestry 5.1.0.5 (haven't had the time to try
5
Hi,
Yes, I'm working with incoming links. The code I have so far:
public class PageLinkTransformer implements PageRenderLinkTransformer {
<...>
private static final Pattern REGEX_NODE_PATTERN =
Pattern.compile("/page/(\\d++)");
<…>
public PageRenderRequestPa
Hi,
you need to provide some more details. Are you trying to rewrite incoming
URLs?
2010/9/7 Marek Stanisław Wawrzyczny
> Hi everyone,
>
> I hope you can help a Tapestry newbie here :)
>
> I've been following the blog post on how to use the new API (we're
> developing a new app in 5.2)
> http:/
Hi everyone,
I hope you can help a Tapestry newbie here :)
I've been following the blog post on how to use the new API (we're developing a
new app in 5.2)
http://blog.tapestry5.de/index.php/2010/09/06/new-url-rewriting-api/ but for
the life of me I can't figure out how to pass extracted URL pa
