> though it implements the HttpSessionBindingListener and not the > HttpSessionListener. > i guess the difference between both ist, that the binding listener only > realizes and observes which > values of the session are bound and the session listener recognizes if a > session itself is created > or destroyed.
Yep. Another difference is that HttpSessionListener needs to be configured in web.xml and HttpSessionBindingListener doesn't. So from Wicket's point of view, HttpSessionBindingListener works good because clients don't need to know about it. But HttpSessionListener might be more what you want, in which case you can simply implement and install it. Eelco ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
