Mike Duffy wrote:
One aspect of JSF which I find troubling is, "With JSF, the component model takes care of all the
responsibilities that Struts uses an ActionForm form, so you don't need one any more." Most of the JSF examples I've studied use method (2) from Craig's list below: "You can bind
component *values* directly to properties in your backing bean, and then provide the business
logic as action methods in the same class." As an example of this approach see, Developing Web
Interfaces with JSF,
http://www.fawcette.com/javapro/2004_01/magazine/features/cschalk/default.aspx
IMHO, mixing business logic in the backing bean is not a great design. I like the clean separation
provided by the Struts action class.
Spring's front end web framework also doesn't have the concept of an ActionForm and you can bind your VO to the form fields. I love this idea (Overall, I haven't found Spring's web framework component to be much benefit over Struts, though). I think the concept of an ActionForm is over-kill and a waste. Binding a VO to the front end, though, doesn't mean you are "mixing business logic in the backing bean." There are intermediate steps (injected filters, etc) that will do the conversions and actually binding, similar to what you have to do anyway in an Action class using BeanUtils or else manually setting your VO from ActionForm fields.
-- Rick
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
