You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Fritz Pröbstle (JIRA)" <ji...@apache.org> on 2009/05/26 13:03:46 UTC
[jira] Created: (TAP5-718) Multiple calld of onPassivate
Multiple calld of onPassivate
------------------------------
Key: TAP5-718
URL: https://issues.apache.org/jira/browse/TAP5-718
Project: Tapestry 5
Issue Type: Bug
Components: tapestry-core
Affects Versions: 5.1.0.5
Reporter: Fritz Pröbstle
The Page Render Request onPassivate is called for evey component im the page.
This is definitly not what is documented in http://tapestry.apache.org/tapestry5/tapestry-core/guide/pagenav.html.
This means you have multiple calls to onPassivate for a single page passivation.
Therefor the onPassivate in not usable for cleaning up etc. because you never knoe how many times it is called.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (TAP5-718) Multiple calld of onPassivate
Posted by "Robert Zeigler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Zeigler closed TAP5-718.
-------------------------------
Resolution: Invalid
> Multiple calld of onPassivate
> ------------------------------
>
> Key: TAP5-718
> URL: https://issues.apache.org/jira/browse/TAP5-718
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.1.0.5
> Reporter: Fritz Pröbstle
>
> The Page Render Request onPassivate is called for evey component im the page.
> This is definitly not what is documented in http://tapestry.apache.org/tapestry5/tapestry-core/guide/pagenav.html.
> This means you have multiple calls to onPassivate for a single page passivation.
> Therefor the onPassivate in not usable for cleaning up etc. because you never knoe how many times it is called.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (TAP5-718) Multiple calld of onPassivate
Posted by "Robert Zeigler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Robert Zeigler closed TAP5-718.
-------------------------------
Resolution: Invalid
> Multiple calld of onPassivate
> ------------------------------
>
> Key: TAP5-718
> URL: https://issues.apache.org/jira/browse/TAP5-718
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.1.0.5
> Reporter: Fritz Pröbstle
>
> The Page Render Request onPassivate is called for evey component im the page.
> This is definitly not what is documented in http://tapestry.apache.org/tapestry5/tapestry-core/guide/pagenav.html.
> This means you have multiple calls to onPassivate for a single page passivation.
> Therefor the onPassivate in not usable for cleaning up etc. because you never knoe how many times it is called.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (TAP5-718) Multiple calld of onPassivate
Posted by "Robert Zeigler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12713073#action_12713073 ]
Robert Zeigler commented on TAP5-718:
-------------------------------------
onPassivate was NEVER intended to be used as a "cleanup method". For that, use cleanupRender (or the @CleanupRender annotation). See:
http://tapestry.apache.org/tapestry5/guide/rendering.html
> Multiple calld of onPassivate
> ------------------------------
>
> Key: TAP5-718
> URL: https://issues.apache.org/jira/browse/TAP5-718
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.1.0.5
> Reporter: Fritz Pröbstle
>
> The Page Render Request onPassivate is called for evey component im the page.
> This is definitly not what is documented in http://tapestry.apache.org/tapestry5/tapestry-core/guide/pagenav.html.
> This means you have multiple calls to onPassivate for a single page passivation.
> Therefor the onPassivate in not usable for cleaning up etc. because you never knoe how many times it is called.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (TAP5-718) Multiple calld of onPassivate
Posted by "Robert Zeigler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/TAP5-718?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12713073#action_12713073 ]
Robert Zeigler commented on TAP5-718:
-------------------------------------
onPassivate was NEVER intended to be used as a "cleanup method". For that, use cleanupRender (or the @CleanupRender annotation). See:
http://tapestry.apache.org/tapestry5/guide/rendering.html
> Multiple calld of onPassivate
> ------------------------------
>
> Key: TAP5-718
> URL: https://issues.apache.org/jira/browse/TAP5-718
> Project: Tapestry 5
> Issue Type: Bug
> Components: tapestry-core
> Affects Versions: 5.1.0.5
> Reporter: Fritz Pröbstle
>
> The Page Render Request onPassivate is called for evey component im the page.
> This is definitly not what is documented in http://tapestry.apache.org/tapestry5/tapestry-core/guide/pagenav.html.
> This means you have multiple calls to onPassivate for a single page passivation.
> Therefor the onPassivate in not usable for cleaning up etc. because you never knoe how many times it is called.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.