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 2010/08/05 22:00:16 UTC
[jira] Created: (TAP5-1235) The interaction between a Form
component and the active page can be problematic when there is an error
loading a page
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.
[jira] Commented: (TAP5-1235) The interaction between a Form
component and the active page can be problematic when there is an error
loading a page
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12899778#action_12899778 ]
Hudson commented on TAP5-1235:
------------------------------
Integrated in tapestry-5.2-freestyle #173 (See [https://hudson.apache.org/hudson/job/tapestry-5.2-freestyle/173/])
TAP5-1235: The interaction between a Form component and the active page can be problematic when there is an error loading a page
> 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
> Assignee: Howard M. Lewis Ship
> Fix For: 5.2.1
>
>
> 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.
[jira] Assigned: (TAP5-1235) The interaction between a Form
component and the active page can be problematic when there is an error
loading a page
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship reassigned TAP5-1235:
------------------------------------------
Assignee: Howard M. Lewis Ship
> 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
> Assignee: 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.
[jira] Commented: (TAP5-1235) The interaction between a Form
component and the active page can be problematic when there is an error
loading a page
Posted by "Christophe Cordenier (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (TAP5-1235) The interaction between a Form
component and the active page can be problematic when there is an error
loading a page
Posted by "Igor Drobiazko (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12895777#action_12895777 ]
Igor Drobiazko commented on TAP5-1235:
--------------------------------------
This issue is related to TAP5-1234
> 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.
[jira] Closed: (TAP5-1235) The interaction between a Form component
and the active page can be problematic when there is an error loading a
page
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship closed TAP5-1235.
--------------------------------------
Fix Version/s: 5.2.1
Resolution: Fixed
> 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
> Assignee: Howard M. Lewis Ship
> Fix For: 5.2.1
>
>
> 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.
[jira] Commented: (TAP5-1235) The interaction between a Form
component and the active page can be problematic when there is an error
loading a page
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12899778#action_12899778 ]
Hudson commented on TAP5-1235:
------------------------------
Integrated in tapestry-5.2-freestyle #173 (See [https://hudson.apache.org/hudson/job/tapestry-5.2-freestyle/173/])
TAP5-1235: The interaction between a Form component and the active page can be problematic when there is an error loading a page
> 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
> Assignee: Howard M. Lewis Ship
> Fix For: 5.2.1
>
>
> 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.
[jira] Assigned: (TAP5-1235) The interaction between a Form
component and the active page can be problematic when there is an error
loading a page
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship reassigned TAP5-1235:
------------------------------------------
Assignee: Howard M. Lewis Ship
> 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
> Assignee: 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.
[jira] Commented: (TAP5-1235) The interaction between a Form
component and the active page can be problematic when there is an error
loading a page
Posted by "Igor Drobiazko (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12895777#action_12895777 ]
Igor Drobiazko commented on TAP5-1235:
--------------------------------------
This issue is related to TAP5-1234
> 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.
[jira] Issue Comment Edited: (TAP5-1235) The interaction between a
Form component and the active page can be problematic when there is an
error loading a page
Posted by "Christophe Cordenier (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12896008#action_12896008 ]
Christophe Cordenier edited comment on TAP5-1235 at 8/6/10 5:40 AM:
--------------------------------------------------------------------
This is also related to TAP5-1201
We have to consider the loopback feature too
was (Author: ccordenier):
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.
[jira] Issue Comment Edited: (TAP5-1235) The interaction between a
Form component and the active page can be problematic when there is an
error loading a page
Posted by "Christophe Cordenier (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12896008#action_12896008 ]
Christophe Cordenier edited comment on TAP5-1235 at 8/6/10 5:40 AM:
--------------------------------------------------------------------
This is also related to TAP5-1201
We have to consider the loopback feature too
was (Author: ccordenier):
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.
[jira] Closed: (TAP5-1235) The interaction between a Form component
and the active page can be problematic when there is an error loading a
page
Posted by "Howard M. Lewis Ship (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-1235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Howard M. Lewis Ship closed TAP5-1235.
--------------------------------------
Fix Version/s: 5.2.1
Resolution: Fixed
> 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
> Assignee: Howard M. Lewis Ship
> Fix For: 5.2.1
>
>
> 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.
[jira] Commented: (TAP5-1235) The interaction between a Form
component and the active page can be problematic when there is an error
loading a page
Posted by "Christophe Cordenier (JIRA)" <ji...@apache.org>.
[ 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.