If think your use case is different. Wicket always creates a session
because it maintains the component hierarchy across requests. Your
component could very easily be based on a shared model maintained in
the session and you don't have to care about relasing it from session,
because wicket takes care of releasing the session (and your model).
IMO it is straightforward and very easy.
.
Juergen
Yes you are absolutely right. Wicket is realy very easy to use. Thanks for
the help.
Christian
___________________________________________________________
Gesendet von Yahoo! Mail - Jetzt mit 1GB Speicher kostenlos - Hier anmelden: http://mail.yahoo.de
-------------------------------------------------------
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
