Hi,
Maybe just a method like Page.onExpired() that you can put code
in? Then when a Page is expired from a PageMap, you could do
something (like this) in terms of cleanup.
This would make it possible to get around these kinds of page
expiration problems. If you say Wicket will never support using Page
objects in the component hierarchy this seems to be reasonable
solution for it. But I would prefer a way to say: don't store/expire/
manage this Page at all, so it gets cleaned up with my Component.
If Wicket maybe could support Page objects in the component hierarchy
(=nested pages), Wicket could expire nested pages in dependency of
the containing component (by not expiring these Page objects at all
because they should get cleaned up automatically).
Ralf
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
