i was a little confused about your original post on this subject, but then
your followup seemed to confuse me more.
your original post on this subject seems to imply there is an additional
layer, distinct from the Action, where business logic should reside.
then, your follow up seems to confirm that the business logic should reside
in the Action.
my original impression about the struts paradigm (being new to it), was that
all business logic was coded into the Action. the logic would then make
calls to Session, Entity, and Java Beans which would encapsulate the
complexities of specific aspects of the business logic. as an approach, this
seems to make the most sense, compared to trying to put _all_ of the business
logic in some place other than an Action and have the Action call it.
what would you say?
thanks
--e--
On Fri, 07 Dec 2001 05:30:52 -0500, Ted Husted wrote:
>Which makes the answer, implement it in the Action first, where it is
>easy to do, but more because it *is* business logic,
.
.
.
>> So, IMHO, ordering is not something the Action does, or something a tag
>> extension does, is something the business layer does. The Action may
>> select which ordering has been requested by the client, but when the
>> data comes back, it just passes it along.
--------------------------------------------
<argo_tec gmbh>
ed.q.bridges
tel. 089-368179.552
fax 089-368179.79
osterwaldstraße 10
(haus F eingang 21)
80805 münchen
</argo_tec gmbh>
--------------------------------------------
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
