And if you really like DispatchAction go a step further an try
LookupDispatchAction.
Shed.
-Original Message-
From: McDonnell, Colm (MLIM) [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 30, 2004 3:41
To: Struts Users Mailing List
Subject: RE: Searching pattern/best-practise for forms
2004 08:31
To: Struts Users Mailing List
Subject: Re: Searching pattern/best-practise for forms
Hollaway, Shedrick L CIV TRIREFFAC wrote:
> Alexander,
> This should help you understand applying DAO/DTO patterns in a Struts
> app: http://javaboutique.internet.com/tutorials/ApacheDAOs/
>
Hollaway, Shedrick L CIV TRIREFFAC wrote:
Alexander,
This should help you understand applying DAO/DTO patterns in a Struts
app: http://javaboutique.internet.com/tutorials/ApacheDAOs/
Shed.
Thanks for all your replys and suggestions, but I'm afraid I didn't ask
the right question. What I really wan
List
Subject: RE: Searching pattern/best-practise for forms
That should be:
public EmployeeDTO create(EmployeeDTO employee)
Thinking and typing at the same time. ;-)
> -Original Message-
> From: Dahnke, Eric (Company IT)
> Sen
And if actionForms just used reflection ( to detect if there was a
validate method ) or had to implement an interface rather than having
to inherit from a base class you and everyone else wouldn't have to do
this ...
--b
> Then lookin into the DispatchAction class of struts, and you'll need
Mailing List
> Subject: RE: Searching pattern/best-practise for forms
>
>
>
> Look into the DAO pattern. Create, for example, an
> EmployeeDTO (transport object) and an EmployeeDAO class with
> create(EmployeeDTO employee), update(EmployeeDTO employee),
> delete(Employe
Look into the DAO pattern. Create, for example, an EmployeeDTO
(transport object) and an EmployeeDAO class with create(EmployeeDTO
employee), update(EmployeeDTO employee), delete(EmployeeDTO employee)
and getById(...) - is also a crucial method in the DAO pattern.
Here's the create method for exa
7 matches
Mail list logo
