Hello Matthew;
difficulty in getting WO to serialize sessions, working with the
distributable. element, and so on.
When I've experimented with this, I have turned off session
serialisation between containers. If you look at the snippet from
the WOServletSessionStore below, you will see a bit saying "however,
this functionality may not be completed".
----
This is a subclass of WOSessionStore, and is intended to replace the
WOServerSessionStore subclass. The intention is that WOSessions will
be piggybacked on HttpSession objects from the JSP/Servlet world. As
they expire, so will the WOSessions. If they are serialized and moved
to another container, the WOSession should follow it -- however, this
functionality may not be completed. Because of this, this session
store does not actually store sessions. Instead, it knows how to add/
remove sessions to/from existing JSP sessions. One consequence is
that the WOSessionTimeout setting is no longer applicable, as the JSP
session setting will be used instead.
----
Does anyone have any experience in getting Tomcat to work with WO
in a clustering mode?
http://homepage.mac.com/andrewlindesay/le/articles/wo-tomcat.pdf
cheers.
___
Andrew Lindesay
www.lindesay.co.nz
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
