I would be okay with this if I considered EmployeeActionHelper as
presentation tier object. In fact, since this is getting an
EmployeeForm object, I'd package it with the rest of my Struts classes
(if that's how the package layout worked on the project). To me,
EmployeeActionHelper wouldn't be another layer then.
Hubert
On 7/12/05, Durham David R Jr Ctr 805 CSPTS/SCE
<[EMAIL PROTECTED]> wrote:
> <snip>
>
> > So what happens is the Action looks like...
> >
> > //EmployeeAction
> > execute(...) or dispatchmethod() {
> > EmployeForm empForm = (EmployeeForm)form;
> > //validate form, if success proceed..
> > boolean success = EmployeeActionHelper.updateEmployee(
> > empForm, request );
> > //messages set up based on success or failure
> > }
>
>
> Rick, I don't like it. :) Seriously, you've created a dependency on
> Struts in your business layer, and IMO, that's a big no-no. For my
> part, I do something similar, which I posted about yesterday-- I use
> DynaForms and cast my ActionForms to DynaBeans before passing to the
> business layer. This way, I have a dependency on BeanUtils in the
> business layer, but not on Struts.
>
>
> - Dave
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
