Re: Design Question
Re: Design Question
- Subject: Re: Design Question
- From: Arturo Pérez <email@hidden>
- Date: Thu, 22 Jul 2004 19:55:25 -0400
On Jul 22, 2004, at 6:19 PM, James Cicenia wrote:
Putting my logic in both my Business Class and in a manager class is
where I will head. When I did start refactoring I felt that some of
the logic did not belong in the Business Class and that is where my
"shadow" class or your manager class got started... I thought at this
point I better ask the pros. I will continue the approach of moving
my logic to both the EOs and the Manager classes.
One thing I've observed when doing this that I would caution you
against. Many implementations of manager/workflow/business process
objects confuse themselves with what the underlying EO/business object
should be doing.
Easy to describe examples are tough to come up with. One thought I had
to explain this was the difference between "logging in" and
"associating a user with a session." But I'm not sure that works.
Perhaps "accessing a resource" and "instantiating a resource." In the
former, a manager class may need to be concerned with access control,
resource location determination, etc. In the latter it's just logic in
the constructor for ensuring that the resource is properly
instantiated.
One way to distinguish is that a manager class
mediates/choreographs/workflows the interaction amongst several other
classes that are peers (as opposed to subclasses/part-of/has-of). HTH.
----
WO in philadelphia - wanna cheesesteak with that?
Please visit webobjects.meetup.com.
_______________________________________________
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.