> Sounds like you are generating a form bean from your POJO also - so > where is the "dyna" in that? I guess I'm still missing something. > > Draw me a diagram... like: > > POJO -> struts-config -> ....
So, I don't think this ever got explained. I wrote this little extension so that I could define the DynaForms in my POJOs, saving me the hassle of editing the struts-forms.xml merge file in addition to the POJO when I want to add/remove/change a field. (Laziness, impatience, hubris...) Why didn't I just use ActionForms? I didn't feel like writing them, and I wasn't able to get the existing struts.form stuff working outside of an EJB. In addition to that, I have a pretty handy DynaForm subclass that does a lot of the heavy lifting for me that normal ActionForms generally provide. I was also able to get the DynaForm stuff working without changing any code, just a few templates. The path looks like: POJO -> (struts-config.xml, hibernate mapping) I would like to add in support for the Validator tags, and probably will once I have some free time. Which brings up another issue... I plan on continuing to make improvements to the extension that I wrote. If I shouldn't call the distributed file "xdoclet-whatever", please let me know. I don't care if the code is adopted by the XDoclet team, which, given the apparent hostility to it, seems generally unlikely. Thanks for your time. If there are specific questions or feature requests, please feel free to email me directly. -- Nick Heudecker System Mobile, Inc. Email: [EMAIL PROTECTED] Web: http://www.systemmobile.com ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user
