You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Jochen Kemnade (JIRA)" <ji...@apache.org> on 2015/01/12 09:10:59 UTC
[jira] [Closed] (TAP5-851) Very hard to add new lifecycle behaviors
to pages & components
[ https://issues.apache.org/jira/browse/TAP5-851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jochen Kemnade closed TAP5-851.
-------------------------------
Resolution: Invalid
We assume this is no longer relevant and therefore close it.
If you still have this issue in a recent Tapestry version (such as 5.3.8 or the latest 5.4 preview release), feel free to provide the necessary information and reopen.
> Very hard to add new lifecycle behaviors to pages & components
> --------------------------------------------------------------
>
> Key: TAP5-851
> URL: https://issues.apache.org/jira/browse/TAP5-851
> Project: Tapestry 5
> Issue Type: Improvement
> Components: tapestry-core
> Affects Versions: 5.2
> Reporter: Howard M. Lewis Ship
> Labels: bulk-close-candidate
>
> Taked with creating a new kind of lifecycle event, one that detects when the active page has changed, I found I had much trouble extending the default behavior, which involved overriding internal services and implementing internal interfaces.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)