It's exactly the "lazy" part of the functionality that I need. I have a large and arbitrary (because they can be defined by the user) set of classes that need fields populated inside them to configure them. I'm assembling the forms to get the user input based on the heirarchy of the class - they all extend StatisticalAnalysis, so I include the .jsp fragment that presents form fields for configuring that class's members, and then many of them also extend FilteredAnalysis, so I intelligiently include or don't include the jsp fragment for that, etc. There's no way I can hope to keep the struts-config.xml up to date with all the fields and potentially massive number of different forms (also, by assembling the forms from fragments, it's helpful for them to all use the same form name/type).
During the interim between my last post and your reply, I found a LazyDynaActionForm implementation at http://wiki.apache.org/struts/StrutsCatalogLazyList, which I came across while searching for an answer to the exception I mentioned in my last post. Unfortunately, when using that, I get a "javax.servlet.jsp.JspException: No getter method available for property filterField for bean under name org.apache.struts.taglib.html.BEAN". I'll ask around the lab about the commons-validator thing... I'm not in charge of the libraries that get distributed to the developers; if I can get that resolved, maybe I won't have to deal with this new class. Thanks very much for your help, Ryan -- View this message in context: http://www.nabble.com/how-do-I-use-a-LazyDynaBean-as-an-ActionForm--tf1925661.html#a5275174 Sent from the Struts - User forum at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
