On Thu, 21 Feb 2002, Porter, Roy wrote:
> Date: Thu, 21 Feb 2002 17:49:03 -0000
> From: "Porter, Roy" <[EMAIL PROTECTED]>
> Reply-To: Struts Developers List <[EMAIL PROTECTED]>
> To: 'Struts Developers List' <[EMAIL PROTECTED]>
> Subject: RE: DynaActionFormClass & set-property
>
> Answer in line ...
>
> > > I'm trying to add regular Javabean style properties, as
> > well as dynamic
> > > properties.
> > >
> >
> > Ah ... then you're not going to like the current implementations of
> > DynaBeans very much. They currently represent themselves as
> > having *only*
> > the set of dynamic properties that are defined.
> >
> > > an excerpt from the struts-config would be something like:
> > >
> > > <form-bean name="AddressForm" type="com.xxxxx.XXDynaActionForm"
> > > dynamic="true"
> > className="com.xxxxx.struts.config.XXFormBeanConfig" >
> > > <set-property property="voClassName"
> > > value="com.xxxxx.AddressTypeVO"/>
> > > <set-property property="converterClassName"
> > > value="com.xxxxx.AddressType"/>
> > > <form-property name="add1" type="java.lang.String"/>
> > > <form-property name="add2" type="java.lang.String"/>
> > > <form-property name="add3" type="java.lang.String"/>
> > > </form-bean>
> > >
> > > So in effect, the XXDynaActionForm class simply adds 2
> > properties to the
> > > standard DynaActionForm, and likewise for the
> > XXFormBeanConfig class.
> > >
> >
> > What makes voClassName and converterClassName any different
> > than any other
> > dynamic property? Why can't you just declare them with
> > <form-property>
> > elements like "add1", "add2", and "add3"?
>
> The voClassName etc. are set in the struts config file so that we can
> determine what type value object to create from each form. In effect, they
> are static fields.
>
You can use the "initial" attribute on <form-property> for things like
this, as long as the underlying properties are Strings or primitives. The
reset() method sets everything back to the specified initial value.
> >
> > > According the 1.1 dtd this is allowable.
> > >
> > > If it's not obvious from the above, what I'm trying to do
> > is to write as
> > > little code as possible ....
> > > there'll be the one ActionFormClass, using dynamic
> > properties. As the
> > > project is using EJB, the Action class will convert the
> > dynamic properties
> > > to the relevant Value Object type using the specifined
> > converter, before
> > > invoking the required business object.
> > >
> > > I could have the voClassName, and converterClassName as
> > form-property's with
> > > an initial value. But, would these not then get cleared on
> > calling the reset
> > > method ?
> > >
> >
> > If you declared them as standard dynamic properties (with
> > <form-property>), they would get initialized (and cleared) to null.
>
> According to the dtd there's an initial attribute on the form-property tag,
> I take it I could use this property, and then override the reset method to
> ensure that my 'static' fields remain at their initial values ?
>
You don't even have to override ... the standard reset() method in
DynaActionForm does this for you.
> I'm not an expert with dtd's, but am wondering if it is possible to not
> allow set-property tag's under the form-bean tag, if the form-bean is set to
> dynamic ? As it seems they are not supported, this would make sense, if
> possible ?
>
DTDs don't give you that sort of expressive power, unfortunately. If/when
we ever get to using an XML Schema for validation, this would be possible.
> Roy.
>
Craig
> --
> To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
>
>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
