this is how free I felt:
https://issues.apache.org/jira/browse/WICKET-2321
I'd be looking forward for that especially in the context of Ajax and
keeping control over JavaScript objects on the browser side. Like
components that induce the instation of JavaScript objects in the
Browser. These should outlive the Component#detach() but be cleaned up
on removal of the Component. From my perspective the given patch would
be a good way to go.
mf
Am 08.06.2009 um 18:27 schrieb Igor Vaynberg:
On Sun, Jun 7, 2009 at 10:40 AM, Martin
Funk<mafulaf...@googlemail.com> wrote:
Hi list,
in short:
Why is there no Component#onRemove() method?
because no one asked for it. feel free to create a jira issue with
the request.
-igor
I see that there is Component#onDetach() which is called by
Component#remove(), so it might be a good candidate.
But onDetach is also called at the end of every RequestCycle.
I have things that I want to get done when a Component is removed or
replaced, not on every detach.
How can I achieve that?
mf
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
