I recall a discussion of this in the recent past (search the
archives) but fail to recall the cause. Where exactly is the session
getting created? Maybe that will remind me. Logging out a stack
trace from the session constructor is a big help:
public Session() {
super();
NSLog.out.appendln(new RuntimeException(Session Created Here);
...
Chuck
On Nov 7, 2005, at 7:19 PM, Greg Hulands wrote:
Hi,
In my application I have found where a new session is getting
created, but it shouldn't be. I have logged out the sessionID from
the context().request(), but when I do session(), it is creating a
new session, even though there is a session id in the request.
Under what circumstances does a new session get created? I guess a
work around would be to restore the session myself using the
sessionID from the request, but I would really like to know why it
would be occurring.
Any information is greatly appreciated.
Regards,
Greg
___
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/chill%
40global-village.net
This email sent to [EMAIL PROTECTED]
--
Coming in 2006 - an introduction to web applications using WebObjects
and Xcode http://www.global-village.net/wointro
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems.http://www.global-village.net/products/practical_webobjects
___
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to archive@mail-archive.com
