Hello, Marco,
First, Struts merely adds to your options. Struts is not invasive. You don't have to use it at any time.
Second, I find Struts to be absolutely reliable and easy to use. If you understand how it works, it is also really, really flexible. I worry sometimes that they will try to add too much to Struts and ruin its fairly simple and very useful structure. Essentially the Struts framework consists of Actions which have mappings using Forms, Forwards, Errors, Messages, etc. Any of this can be overridden at any time with an understanding of the workings. I personally find Forms to be of immense use and are especially useful if they are used only for data mining and setting and not for data persistence.
I cannot imagine why you would not want to use ActionForms.
Marco Tedone wrote:
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?
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]
