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


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: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to