Re: getting to know Mr. ERXRoute
Re: getting to know Mr. ERXRoute
- Subject: Re: getting to know Mr. ERXRoute
- From: Mark Wardle <email@hidden>
- Date: Fri, 31 Dec 2010 10:54:23 +0000
The CoreBusinessLogic actor is usually set during login during my
interactive apps.
ie there is no magic going on - the setter is simply a way of creating
something within ERXThreadStorage.
IMHO, the business logic code should be separate from the controller
code - and I perceive the idea of the currently logged in user to
definitely be a controller thing. Sometimes it is difficult to
conceive of a time when you won't want to set the user to the
currently logged in user, but it does tie down your implementation to
the notion of a currently logged in user!
I'm not next to computer at the moment so I can't check the source to
suggest a quick fix.
Mark
--
Dr. Mark Wardle
Specialist registrar, Neurology
(Sent from my mobile)
On 30 Dec 2010, at 20:47, Jesse Tayler <email@hidden> wrote:
> sorry, indeed, I left some hacks in code on create methods of the UserController,
>
> creating a post does work: but only if I don't use the corebiz method in the eo's init
>
> so, I still wonder which method of eo relationship creation is best for both web and webservices?
>
> is this setAuthorRelationship style the preferred way?
>
> On Dec 30, 2010, at 2:48 PM, Jesse Tayler wrote:
>
>> setAuthorRelationship((User) ((User)ERCoreBusinessLogic.actor()).localInstanceIn(editingContext()));
>
> _______________________________________________
> 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
_______________________________________________
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