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.

In any case, I do think something strange is happening within Tapestry (bet
you've never heard that before).

1. I think I'm contributing my dispatcher after the asset dispatcher (see
below).
2. When the problem occurs, decodePageRenderRequest does returns a non-null
value for asset paths like /assets/.../whatever.css, with the logical name
of my index page.
3. The problem only manifests once any of the page classes are
auto-reloaded by Tapestry (e.g. if I edit a .tml file).

Here's how I'm contributing the dispatcher from my module:

public void contributeMasterDispatcher(
OrderedConfiguration<Dispatcher> configuration,
 @InjectService("PageAuth") Dispatcher pageAuth) {
configuration.add("PageAuth", pageAuth, "before:PageRender");
}

Michael

On 23 August 2012 21:26, Thiago H de Paula Figueiredo <thiag...@gmail.com>wrote:

> On Thu, 23 Aug 2012 17:29:13 -0300, Michael Prescott <
> michael.r.presc...@gmail.com> wrote:
>
>  Hey there,
>>
>
> Hi!
>
>
>  This approach clearly isn't correct, however, because for asset requests,
>> it returns my Index page.  (Though, not always!)
>>
>
> I think implementing RequestFilter or using Tapestry Security are better
> suited than a Dispatcher for that, but, anyway, your problem is that you're
> probably adding your Dispatcher before the Asset one. Make sure your
> Dispatcher.dispatch() method returns false when the request is not for a
> page (i.e. ComponentEventLinkEncoder.**decodePageRenderRequest(**request)
> returns null).
>
> --
> 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
>
>

Reply via email to