I already commited a fix that would generate a more useful message in
this situation. I always think an NPE from inside Tapestry is a big
failure.
On Thu, Oct 14, 2010 at 9:25 AM, Manuel Sugawara
wrote:
> On Wed, Oct 13, 2010 at 2:30 PM, Howard Lewis Ship wrote:
>
>> See https://issues.apache.o
On Wed, Oct 13, 2010 at 2:30 PM, Howard Lewis Ship wrote:
> See https://issues.apache.org/jira/browse/TAP5-1304
>
> Basically, the Request service isn't set up yet in the method you are
> invoking.
>
> Most likely, you want to contribute a filter to the RequestHandler
> service pipeline, not the
See https://issues.apache.org/jira/browse/TAP5-1304
Basically, the Request service isn't set up yet in the method you are invoking.
Most likely, you want to contribute a filter to the RequestHandler
service pipeline, not the HttpServletRequestHandler pipeline.
On Wed, Oct 13, 2010 at 11:57 AM, M
Hi all,
Using tapestry 5.2.1. I have a filter that serves resources to clients
(images, documents, etc). This filter uses an injected service to check if
the user has the required permission to download the resource, but this is
not working as expected. The authorization filter throws an exception
