On Fri, Feb 6, 2009 at 9:49 AM, Jonathan O'Connor wrote:
> Thiago,
> firstly, I assumed you meant "Normal" == "the Tapestry Dispatcher", but my
> point is that the 4 Tapestry built-in Dispatchers (AssetDispatcher,
> ComponentEventDispatcher, PageRenderDispatcher and RootPathDispatcher) are
> no di
Thiago,
firstly, I assumed you meant "Normal" == "the Tapestry Dispatcher", but
my point is that the 4 Tapestry built-in Dispatchers (AssetDispatcher,
ComponentEventDispatcher, PageRenderDispatcher and RootPathDispatcher)
are no different to my JonathansFunkyDispatcher, and nor should they.
An
On Thu, Feb 5, 2009 at 10:43 PM, Jonathan O'Connor wrote:
> Thiago,
Hi!
> I guess you want the Class if your doing annotation based protection, and
> the string if you have some sort of map.
You're right. My needs are different from yours. :)
> But, as Daniel mentioned, you can
> get a Compone
Howard,
this saves me any more cogitation for now!
Ciao,
Jonathan
On 05/02/2009 20:11, Howard Lewis Ship wrote:
The ComponentRequestHandler pipeline (new in 5.1) is for this purpose.
You can contribute a ComponentRequestFilter; your filter is passed
all the details of the request (page names,
Thiago,
I guess you want the Class if your doing annotation based protection,
and the string if you have some sort of map. But, as Daniel mentioned,
you can get a ComponentSource, and convert the string to a Class, so no
problems there.
The problem is deciding what a normally dispatched reque
The ComponentRequestHandler pipeline (new in 5.1) is for this purpose.
You can contribute a ComponentRequestFilter; your filter is passed
all the details of the request (page names, nested ids, page
activation context, event context) and can decide how to proceed.
CRH pipeline is a facade around
Em Thu, 05 Feb 2009 15:20:02 -0300, Jonathan O'Connor
escreveu:
Thiago,
Hi!
I thought about the service idea, but what would it look like?
Class extractPageClass(String requestPath) would be what I'd want.
That's what I want too. I would add a String extractPageName(String
reques
?
>>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
> For additional commands, e-mail: users-h...@tapestry.apache.org
&g
Thiago,
I thought about the service idea, but what would it look like?
Class extractPageClass(String requestPath) would be what I'd want.
However, for each Dispatcher, you'd want a PageClassExtracter as well,
and I'm sure there'd be lots of duplication. To stay DRY, I guess we
have to add t
Em Thu, 05 Feb 2009 07:40:24 -0300, Jonathan O'Connor
escreveu:
Daniel,
I was looking at this problem the other day, and you should look at the
ComponentEventDispatcher. I think you need to first check if you get a
matching page, and then check if you have an event. You can then extract
2:00 Athens, Beirut, Bucharest,
Istanbul
Subject: Re: Protecting ActionLinks when using a Dispatcher.
Daniel,
I was looking at this problem the other day, and you should look at the
ComponentEventDispatcher. I think you need to first check if you get a
matching page, and then check if you have an event
Daniel,
I was looking at this problem the other day, and you should look at the
ComponentEventDispatcher. I think you need to first check if you get a
matching page, and then check if you have an event. You can then extract
the Pagename from the request path using that monster Reg exp. Sadly,
want
to extend base classes or mess about with onActivate() so ideally I would
like a solution that is similar to the dispatcher or some sort of filter.
Many Thanks,
Daniel
--
View this message in context:
http://www.nabble.com/Protecting-ActionLinks-when-using-a-Dispatcher.-tp21848757p218487
13 matches
Mail list logo
