Re: Application terminates when a session times out
Re: Application terminates when a session times out
- Subject: Re: Application terminates when a session times out
- From: Art Isbell <email@hidden>
- Date: Fri, 14 Feb 2003 12:43:10 -1000
On Friday, February 14, 2003, at 12:10 PM, meena wrote:
Are you fetching it in a session and then setting it as a
universal user?
Yes, this is exactly what I am doing.
Then Seejo is correct in his analysis.
After fetching the IA_User object
in the session's defaultEditingContext, I am storing this object at the
Application level.
Yeah, that won't work after the editing context in which you fetched
the user is finalized.
a. How can I initialize such application objects if it should not
done be
through a session ?
You could use an EOSharedEditingContext in Application and fetch it
into there. See the EOSharedEditingContext JavaDoc to see whether your
use of the user object meets its restrictions. Sounds like it might.
You could also create an EOEditingContext in Application and fetch
user into that, but you would have to fault user into each session's
editing context before you could relate it to any other object. You
wouldn't have to fault it into other editing contexts from a shared
editing context; just treat user as if it were already in the session's
editing context.
b. Is there a way to physically copy such objects from the session to
the
application level so that it is available even after the session is
terminated ?
See EOUtilities.localInstanceOfObject(). But why bother? Just fetch
user in your Application constructor and not bother doing so in Session.
Art Isbell
AppleCare Professional Services Technical Support
http://www.apple.com/services/technicalsupport/
+1-808-591-0836
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.