This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Are there any advantages to using the Dynammically created Form Beans other than not having to write all those getter and setter methods? I like them, I am just curious as to other key benefits. Thanks.
One of the nice things about them is that for people who are not all that familiar with Struts, it may be a bit easier to define your beans via XML. I have found this to be the case when working on development teams with folks who are just beginning to get a grasp on Struts. Another benefit is that the class DynamicActionForm implements org.apache.commons.beanutils.DynaBean, allowing the developer quick use to the Jakarta Commons Bean Introspection Utilities libraries. This allows the developer to easily write generic ways of handling their form beans, regardless of what the bean's properties are. It's funny you bring this up because as we speak I'm staring at a blank Word document, getting ready to write an article on this library.
Originally posted by Jason Menard: It's funny you bring this up because as we speak I'm staring at a blank Word document, getting ready to write an article on this library.
If the article is not for the Newsletter, can you pass it on to me when you complete it. I would like to read it.
Joined: Nov 09, 2000
Originally posted by Gregg Bolinger: If the article is not for the Newsletter, can you pass it on to me when you complete it. I would like to read it.
It would be nice if I get it done in time for the Newsletter, but in any case I will let you take a look at it when I'm done. (if I was unclear btw, I'm talking about an article on the Commons BeanUtil library, not DynaForms)