The reason I often end up using my Value Object directly in my
ActionForm is because rarely do I ever end up with a nice simple case
where the users are submitting simple form fields. Typically I end up
with cases where I have to deal with a bunch of nested beans. It gets
INCREDIBLY cumbersome to try to duplicate the same exact nested
structure with objects in a form bean that need to represent the same
exact nested structure of the objects. I'd be curious for those of you
that 'only' use straight properties in your ActionForm deal with this?
How do you deal with a situation where you have to edit for example a
master detail record that contains nested objects? It's so much easier
dealing with the VOs for this kind of stuff.
--
Rick
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]