Re: Passing variable from DirectAction to Session constructor
Re: Passing variable from DirectAction to Session constructor
- Subject: Re: Passing variable from DirectAction to Session constructor
- From: "Cheong Hee (Gmail-P)" <email@hidden>
- Date: Tue, 21 Apr 2009 12:27:20 +0800
I am using MultiECLockManager whenever savechanges to be done at component
level. Thanks.
Cheers
Cheong Hee
In a normal app everyone shares the same OSC ... This is why you have
to lock. If you're locking properly, I can think of any reason why
this would be a problem.
ms
On Apr 20, 2009, at 6:44 AM, Cheong Hee (Gmail-P) wrote:
Apologize for getting back late as some implications happened on my
tests.
Thanks to Chuck's reply. So far using
createSessionForRequest(WORequest aRequest) in Application and
create new OSC seemed working fine. (Not in Wonder yet.) One issue
to find out is - if it is a good idea to have an static array in
Application to keep a pool of OSCs created by different
organizations. By doing this, this is to ensure the users from same
organization will get back its own OSC. Anyone has tried that and
seen side-effect if the user access respective OSCs (and set
defaultEC) in multi-application instances mode?
Cheers
Cheong Hee
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden