I don't really get this thread at all, especially all the chatter about passing form references.
Seems to me that you either override the RequestProcessor's processActionForm() method and plug in your form factory there, since it returns the ActionForm then there is no issue about references. Its just a question of whether theres enough info in the ActionMapping for your form factory to know what flavour form to create. If you would rather create the ActionForm in the Action's execute method, then again the issue about references is irrelevant since thats the last place the ActionForm is referenced in the RequestProcessor's chain of events. All you would need to do is create the form and store it in the Request/Session under the mapping's attribute name (as it does in the processActionForm() method). The downside of doing this is that you've effectively skipped the ActionForm population mechanism. If you really want to do a dynamic form created on the fly - then do it the easy way (shameless plug), use lazy ActionForms :-) http://www.niallp.pwp.blueyonder.co.uk Niall ----- Original Message ----- From: "Michael McGrady" <[EMAIL PROTECTED]> To: "Struts Users Mailing List" <[EMAIL PROTECTED]> Sent: Friday, August 06, 2004 8:49 PM Subject: GOING GOING GONE DYNAMIC > Is there a way to create or modify the mapping and the form for an action > on the fly? Couldn't we use, for example, a "nude" DynaActionForm with a > name and then (re)instantiate it with > > form = DynamicActionFormFactory.createBlankForm(String name, String type, > String[] fields); > > or something similar and do something like this by grabbing the > ActionMapping class and massaging it as needed as well? > > Anyone have any things like this lying around in the sun? > > Michael McGrady --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
