+1 On Fri, Jun 10, 2011 at 10:52 AM, Emond Papegaaij <emond.papega...@topicus.nl> wrote: > Hi all, > > With the migration from Wicket 1.4 to 1.5, we tried to rewrite our custom > request cycle code into IRequestCycleListeners. This worked for most of our > code, except for one use-case: running code after everything is detached. In > Wicket 1.4, it was possible to use the onAfterTargetsDetached for this, but a > similar method is not available in IRequestCycleListener. > > I opened a ticket for this (WICKET-3695), but it was closed by Igor. After a > bit of discussion (see the issue), he suggested to start a vote here; so here > it is. We would like the addition of onDestroy to IRequestCycleListener, which > is called after everything is detached. This would serve to tear down request > state that is still needed during detaching. > > Best regards, > Emond Papegaaij >
-- Become a Wicket expert, learn from the best: http://wicketinaction.com
