100% right. the jsessionid is for tracking one session. In one session we store 1..n Wicket application objects, one for each application (servlet). Nothing special about it, just something we should do.

This might explain some of the weird stuff I experienced as well. Good job finding this one Juergen!

Eelco

...

, 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

Reply via email to