> > I am more interested in doing this with (Craig's soon to come)
> > DynaActionForm.
> > My end goal is to have one generic form bean (that will work for all
> > actions).
> > For such a generic form bean to handle multi-level properties
> > such as "myProp{MyPropClass}.subProp", it has to infer and
> initialize the
> > first property, so that the setter on the subProp can be invoked.
> >
> > I am interested in knowing your thoughts and opinions on this.
> > If it does work out and I happen to implement it, I will
> provide a patch.
> >
>
> I just checked in the code for DynaActionForm, along with
> support for it
> in Struts. I also added a way to configure the initial value
> for dynamic
> properties that is used in the reset() method. So, you could
> preconfigure
> the logon form's values like this:
>
> <form-bean name="logonForm"
> type="org.apache.struts.action.DynaActionForm">
> <form-property name="username" type="java.lang.String"
> initial="user"/>
> <form-property name="password" type="java.lang.STring"/>
> </form-bean>
>
> much the same as you can preinitialize normal instance variables with
> initial values when the bean is created.
>
> Does that do what you were looking for?
>
That should take care of it. Thank you much, Craig.
I will check it out today.
anil
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
