[
https://issues.apache.org/jira/browse/WICKET-2321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Funk updated WICKET-2321:
--------------------------------
Component/s: wicket
Fix Version/s: 1.4-RC6
Issue Type: Improvement (was: Bug)
Affects Version/s: 1.4-M1
1.4-M2
1.4-M3
1.4-RC1
1.4-RC2
1.4-RC3
1.4-RC4
1.4-RC5
Just throwing in my oppinion about the timeschedule for this request.
Implementing this should be possible for RC6 as it don't break any existing API.
Possibly I'm a little obsessed of this by now, but of corse I think its an
important feature as the livecycle moment of onRemovedFromHirachy is importatn.
Also this can't be worked arround by any idiom.
As I'm running in to the need for this, while I'm trying for, yet another
Google Maps API, component for wicket I do think that this is a good step
helping to implement other JavaScript library componets for wicket.
> create a Component#onRemove() method
> ------------------------------------
>
> Key: WICKET-2321
> URL: https://issues.apache.org/jira/browse/WICKET-2321
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Affects Versions: 1.4-M1, 1.4-M2, 1.4-M3, 1.4-RC1, 1.4-RC2, 1.4-RC3,
> 1.4-RC4, 1.4-RC5
> Reporter: Martin Funk
> Fix For: 1.4-RC6
>
> Attachments: wicket-jira-2321-mf.diff
>
>
> Create a Component#onRemove() method as a hook that may be overriden.
> Sort of like Component#onDetach().
> As the name says It should be invoked when a component or any of its parents
> is removed from the component tree.
> See also:
> http://www.nabble.com/Component-lifecycle-question-td23913399.html
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
