You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Josh Canfield (JIRA)" <ji...@apache.org> on 2010/10/18 06:07:27 UTC

[jira] Commented: (TAP5-986) sendError in onActivate / Tapestry error dispatching

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

Josh Canfield commented on TAP5-986:
------------------------------------

In 5.2 there is an HttpError object that can be returned by an event handler to send an error response to the client. Does that meet the requirements of this defect?

> sendError in onActivate / Tapestry error dispatching
> ----------------------------------------------------
>
>                 Key: TAP5-986
>                 URL: https://issues.apache.org/jira/browse/TAP5-986
>             Project: Tapestry 5
>          Issue Type: Bug
>          Components: tapestry-core
>    Affects Versions: 5.1.0.5
>            Reporter: Christophe Cordenier
>         Attachments: TAP5-986.txt
>
>
> With this kind of configuration in web.xml :
> <filter-mapping>
> 	<filter-name>tapestryFilter</filter-name>
> 	<url-pattern>/*</url-pattern>
> 	<dispatcher>ERROR</dispatcher>
> 	<dispatcher>REQUEST</dispatcher>
> </filter-mapping>
> <error-page>
> 	<error-code>403</error-code>
> 	<location>/error/AccessDenied</location>
> </error-page>
> <error-page>
> 	<error-code>404</error-code>
> 	<location>/error/NotFound</location>
> </error-page>
> RestoreDirtySessionObjects is generating a NullPointerException with this line :
> Session session = request.getSession(false);
> It seems that the dispatching is done in one single thread, then the initial class to RestoreDirtySessionObjects is delay, and request object is lost.

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