RE: Searching pattern/best-practise for forms

2004-11-30 Thread Hollaway, Shedrick L CIV TRIREFFAC
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

RE: Searching pattern/best-practise for forms

2004-11-30 Thread McDonnell, Colm (MLIM)
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/ >

Re: Searching pattern/best-practise for forms

2004-11-30 Thread Alexander Czernay
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

RE: Searching pattern/best-practise for forms

2004-11-29 Thread Hollaway, Shedrick L CIV TRIREFFAC
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

Re: Searching pattern/best-practise for forms

2004-11-29 Thread bryan
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

RE: Searching pattern/best-practise for forms

2004-11-29 Thread Dahnke, Eric (Company IT)
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

RE: Searching pattern/best-practise for forms

2004-11-29 Thread Dahnke, Eric (Company IT)
exander Czernay [mailto:[EMAIL PROTECTED] > Sent: Monday, November 29, 2004 8:30 AM > To: [EMAIL PROTECTED] > Subject: Searching pattern/best-practise for forms > > > I'm searching for a pattern/best-practise for handling standard > data-manipulation forms (like li

Searching pattern/best-practise for forms

2004-11-29 Thread Alexander Czernay
I'm searching for a pattern/best-practise for handling standard data-manipulation forms (like list, create, edit, update, delete functionality) in Struts. I've read about the CRUD (create/read/update/delete) pattern many times, but couldn't find any in-depth papers on it. Is there any recommen