[
https://issues.apache.org/jira/browse/TAP5-1235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12896008#action_12896008
]
Christophe Cordenier commented on TAP5-1235:
--------------------------------------------
This is also related to TAP5-1201
We have to consider also the loopback feature too
> The interaction between a Form component and the active page can be
> problematic when there is an error loading a page
> ---------------------------------------------------------------------------------------------------------------------
>
> Key: TAP5-1235
> URL: https://issues.apache.org/jira/browse/TAP5-1235
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.2.0
> Reporter: Howard M. Lewis Ship
>
> This only occurs when there's an overridden ExceptionReport page, and it
> contains a Form. Presumably, an app that redirects to another application
> page instead of ExceptionReport could also be affected.
> Form uses RequestGlobals.activePageName to fire an event on the active page;
> in an error, that is often the page that could not be loaded. This results in
> another exception and a 500 response to the user. Very hard to track down.
> This could be solved by changing some code to update the active page name
> just as the response starts to render; this would ensure that the Form is
> able to communicate with the correct (rendering) page.
> Also, the Form should be more capable of dealing with no active page
> (RequestGlobals.activePageName is null).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
