Rick,
While you are at it, I suggest you may consider dynamic Forms, DynaActionForm, or Map backed forms, they give you ways to handle form's properties without even knowing the the property names at development time.
Its worth trying.
You mean Robin I think:) since she posted the original question, but since you brought it up, I really don't like any of the Dyna stuff. Not that it isn't sort of cool, but I like to have compile-time checks of my code and ease in refactoring. For example when you use Dyna stuff nothing stops you from doing... myDynaForm.set("firrstName", "Joe") (notice the spelling mistake?) So you'll say use constants like myDynaForm.set(Constants.FIRST_NAME, "Joe") and sure that will help but what does all of this gain you? All of this to simply avoid a few get/set methods which could automatically be generated for you by any average IDE. I'm yet to see the beneift that the Dyna flavors give me. Often times you also end up having to extend the Dyna class for example with DynaForms because you need to implement a reset method.
-- Rick
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
