There is a reason why stuff in BT is done as it is.
I.e. there is a People.class.setCurrentUser(People user) and
People.class.currentUser(EOEditingContext ec). Basically it puts all the thread
storage code (including the key) in People, which is, like, good style?
Also, ERXThreadStorage already handles EOs and faulting.
Cheers, Anjo
Am 14.12.2010 um 21:57 schrieb David Holt:
> public static Person currentUser(EOEditingContext ec) {
> Person currentUser = currentUser();
> if (currentUser != null && currentUser.editingContext() != ec) {
> EOEditingContext currentUserEc =
> currentUser.editingContext();
> currentUserEc.lock();
> try {
> Person localUser = (Person)
> ERXEOControlUtilities
> .localInstanceOfObject(ec,
> currentUser);
> currentUser = localUser;
> } finally {
> currentUserEc.unlock();
> }
> }
> return currentUser;
> }
>
_______________________________________________
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 arch...@mail-archive.com
