I'm configuring my dispatcher with this:
configuration.add("PageAuth", pageAuth, "before:PageRender");
This tells Tapestry to put my pageAuth dispatcher.. *after* page render?
On 24 August 2012 13:44, Thiago H de Paula Figueiredo <thiag...@gmail.com>wrote:
> On Fri, 24 Aug 2012 14:25:01 -0300, Michael Prescott <
> michael.r.presc...@gmail.com> wrote:
>
> Thanks for the reply.
>>
>> I suspect you're right in that a filter is the right way to go. I've used
>> tapestry-security before and fond acegi to have a hilariously complicated
>> domain model for my needs.
>>
>
> I'm talking about Tapestry-Security (http://tynamo.org/tapestry-**
> security%20guide <http://tynamo.org/tapestry-security%20guide>), not the
> Tapestry-Spring-Security. I've never used tapestry-security (from Tynamo)
> myself, but it seems easier to use than Tapestry-Spring-Security, which
> I've used in the past then dropped it.
>
>
> In any case, I do think something strange is happening within Tapestry
>> (bet you've never heard that before).
>>
>
> I don't think so. It's common to put request filters or dispatchers
> without all the needed ordering constraints, and I think that's your case.
>
>
> 1. I think I'm contributing my dispatcher after the asset dispatcher (see
>> below).
>>
>
> You're adding it after PageRender (it should be before) and didn't specify
> anything about the asset dispatcher one.
> You can only be sure the ordering is correct by putting a breakpoint in
> TapestryModule.**buildMasterDispatcher().
>
>
> --
> Thiago H. de Paula Figueiredo
>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail:
> users-unsubscribe@tapestry.**apache.org<users-unsubscr...@tapestry.apache.org>
> For additional commands, e-mail: users-h...@tapestry.apache.org
>
>
