DynaBeans are specified in the Struts-Config. They are not Java classes that an engineer needs to writes.
http://jakarta.apache.org/struts/userGuide/building_controller.html#dyna_action_form_classes A JSP author should be able to define one without any problem. And the one suggested here, could be a standard part of your team's starter Struts config. Heck, if you throw the JSF extension into the mix, I wager you could write significant Struts applications now without writing any Java code at all. :) http://struts.sourceforge.net/struts-bsf/index.html -Ted. On Fri, 16 Jan 2004 11:31:46 -0600, Joe Germuska wrote: > At 11:29 PM -0500 1/15/04, Ted Husted wrote: >> My only comment is that it seems we're throwing a lot of >> technology at a problem that could be solved by putting an empty >> DynaActionForm in the Struts config, and just referring to that. >> Perhaps something like: >> >> <form-bean name="buttonForm" >> type="org.apache.struts.action.DynaForm" /> >> > > That doesn't solve the problem if you want to use html:input tags > when you haven't created the form-beans yet. That's kind of a > corner case, but we are gradually getting non-developers who can > write JSPs and tags ok but haven't yet learned struts-config > syntax. Eventually I hope that they will, and then this might not > be so important. > > I still prefer to err on the side of permissiveness -- a blank form > rather than a stack trace. > > Joe --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
