The external cookie name is defined by the servlet spec and has to be JSESSIONID accross all servlet containers. We should not (and because it is in the spec should not) change it.
You must differentiate between the HTTP session object which is maintained by the servelt container and identified by the session id (JSESSIONID). HTTP session maintains attributes (map). A wicket session is a wicket specific object providing wicket specific functionality. A wicket session object is added to the http session map with attribute name "session". That is, currently there is a one-to-one relationship between http session object and wicket session object. Because of the reasons given, I assume we require a one-to-many relationship. One http session (one per web app) must maintain many wicket sessions (one per servlet per web app). Juergen ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
