>> In Struts, you make this possible by using String properties in the form bean for such fields, and do the conversions later (perhaps in the Action, via a call to something like BeanUtils.copyProperties() from the form bean into your model bean that does the required conversions -- but you know they are going to work). <<
Let me make sure I'm understanding you... what you're saying is that you want to retain the original, unparsed data for a while, because you may need to redisplay it to the user. And if that wasn't the case--i.e. the form bean's setter requires an int, instead of the original String entered by the user--you wouldn't be able to use the form bean to repopulate the form. Once you've validated all the Strings, you can go ahead and copy the form bean into the REAL form bean you want to use, which has typed getters/setters. Sound right? And you're saying that WebWorks actions are http-agnostic, because they are literally just (poorly-encapsulated) objects... you call some setters, then execute. Well, couldn't you just as easily unit-test Struts actions? Instead of calling setters on webwork actions, you're just calling setters on the form bean... (though the ActionMapping seems to be pretty HTTP-specific.) -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
