On May 7, 2007, at 11:18 AM, Mark Morris wrote:
Tom,
I've never had to do this, but I'm pretty sure it can be done.
Someone please jump in and correct any errors, but off the top of
my head I think you need to manually created an EOModelGroup and an
EOObjectStoreCoordinator for your session, associate your model
with the EOModelGroup, and then you can associate the correct
connection dictionary for your user's organization.
I'll just add that the models in each model group need to be
different object instances. The only problem that I know of with
this is that some 3rd party code relies on
EOModelGroup.defaultModelGroup() being the only model group. It is a
bad assumption, but I have seen it made (not, IIRC, in the WO code
itself).
Chuck
Or, maybe better, you can create the new group and coordinator
lazily at the Application level when a user from a particular
organization logs in, and only end up creating at most as many as
you have organizations.
I apologize that this is not very detailed, but hopefully it will
point you in the right direction.
--
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 ([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]
