> -----Original Message----- > From: Marco Tedone [mailto:[EMAIL PROTECTED] > Sent: Tuesday, September 07, 2004 6:53 AM > To: Struts-users > Subject: A couple of questions > > > Hi, in my company we are writing a new J2EE application using > Struts. So far > we've used standard JSP/Servlet technology. HTML forms > processed from within > our Servlets, processing the HttpRequest object. We sent data > to JSPs under > the form of Value Objects which JSTL has managed well. > > Now I'm learning that with Struts there are ActionForm > objects when using > HTML forms: however, although we are fine about using Actions for any > significant "client's action", as regards forms, we would > like to maintain > our current strategy (HTML plain forms processed through > HttpRequest, VOs > and JSTL). > > First question: > > Is there any reason why we shouldnt' maintain our current > approach? Or why > we should use ActionForms?
Because so much of what you're doing in processing the parameters is boilerplate. Why not let the framework put it into an object for you? Then you can use the BeanUtils class to move it itno the VO directly. In much of my code I do: BeanUtils.copyProperties( dataVo, dataForm); and I'm done. Your way would require a lot more code. > > > Second question: > > where could I find the major differences between 1.1 and 1.2? > > > Thank you and regards, > > Marco Tedone > (SCJP, SCBCD) > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
