[jira] [Closed] (TAP5-1755) Keep PageLifecycleListener Methods until replacement is available (or forever)

["Howard M. Lewis Ship (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/TAP5-1755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Howard M. Lewis Ship closed TAP5-1755.
--------------------------------------

       Resolution: Invalid
    Fix Version/s: 5.3.4

At this point, if we do nothing to PageLifecycleCallbackHub we will have addressed your issue.

PageLifecycleListener is still deprecated; I eventually realized that Runnable was the perfect name for a callback of any type.

I've added 5.3.4 to the list of fix versions (far after the fact).


                
> Keep PageLifecycleListener Methods until replacement is available (or forever)
> ------------------------------------------------------------------------------
>
>                 Key: TAP5-1755
>                 URL: https://issues.apache.org/jira/browse/TAP5-1755
>             Project: Tapestry 5
>          Issue Type: Bug
>    Affects Versions: 5.3
>            Reporter: Michael Wyraz
>            Assignee: Howard M. Lewis Ship
>             Fix For: 5.3.4
>
>
> In 5.3, the lifecycle methods in PageLifecycleListener are deprecated and marked as to be removed WITHOUT REPLACEMENT.
> It's clear that by using singletons, there is no real lifecycle anymore but the pages behaves like as there where lifecycle. Removing without replacement will break functionality of third-party extensions that rely on this feature without providing an alternative. So either these functionality should be replaced by a new one or (better) it should be emulated as it is done by the current t5.3 implementation.
> An alternative would be to rename the methods to reflect what's really going on, e.g.:
> containingPageInitialized() and containingPageDisposed()
> Regards, Michael.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira