tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Howard M. Lewis Ship (JIRA)" <j...@apache.org>
Subject [jira] Closed: (TAP5-456) NPE in HttpServletRequestFilter if ApplicationStateManager is used
Date Tue, 03 Mar 2009 22:26:56 GMT

     [ https://issues.apache.org/jira/browse/TAP5-456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Howard M. Lewis Ship closed TAP5-456.
-------------------------------------

    Resolution: Won't Fix
      Assignee: Howard M. Lewis Ship

Previously fixed in 5.1.0.0.

> 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
>            Assignee: Howard M. Lewis Ship
>
> 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.


Mime
View raw message