That is kind of how i found it in the end - log a fatal each time a
session is created with a full stack trace and then trawl through them
looking for something strange.
Simon
On 22 Oct 2008, at 19:18, Chuck Hill wrote:
We aren't calling this method, so I'm trying to understand other
ways such sessions could get created. Any other ideas?
What I always do is to add this to my Session constructor:
NSLog.out.appendln(new RuntimeException("session created"));
Then run your app and look over the many stack traces to find the
ones that are not normal. That should point to where unintended
session creation happens. You could get fancy and create the
exception first, parse the stack trace, and only log if it is not
normal. I will leave that as an exercise for Mike. :-P
Chuck
_______________________________________________
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]
