You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@tapestry.apache.org by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org> on 2009/02/26 18:37:01 UTC

[jira] Commented: (TAP5-456) NPE in HttpServletRequestFilter if ApplicationStateManager is used

    [ https://issues.apache.org/jira/browse/TAP5-456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677071#action_12677071 ] 

Howard M. Lewis Ship commented on TAP5-456:
-------------------------------------------

I'd like to close this as "won't fix" if it has been incidentally fixed in 5.1, which I believe it has.

> NPE in HttpServletRequestFilter if ApplicationStateManager is used
> ------------------------------------------------------------------
>
>                 Key: TAP5-456
>                 URL: https://issues.apache.org/jira/browse/TAP5-456
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.0.18
>            Reporter: Ulrich Stärk
>
> The same problem as described in TAP5-257 holds true for the HttpServletRequestHandler pipeline. If a filter wants to store or retrieve something from the ApplicationStateManager, a NPE is thrown because HttpServletRequest, HttpServletResponse, Request and Response are not stored in the RequestGlobals yet. A workaround is to write a HttpServletRequestFilter that stores these objects into the RequestGlobals service and place it at the very beginning of the pipeline.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.