You could still do them "declaritively" ... read them off an "external"
file.. and *process* it in your setup actions...
 a little more work than you would have liked though! :-)



On 12/5/05, Shivani Sawhney <[EMAIL PROTECTED]> wrote:
>
> Hi,
> Thanks for the reply. There's absolutely no reason that initializing
> field values in setup action won't work for me. But I am building this
> use case for reports and was wondering if the initial values for start
> and end period for every report could be controlled declaratively. But I
> guess I'll just have to use setup action for now.
> Thanks a ton........
>
> Regards,
>
> Shivani
>
>
>
>
>
> -----Original Message-----
> From: Wendy Smoak [mailto:[EMAIL PROTECTED]
> Sent: 05 December, 2005 10:18 AM
> To: Struts Users Mailing List
> Subject: Re: Preserving the query string while validating a form & using
> dynamic initialization with DynaAction
>
> On 12/4/05, Shivani Sawhney <[EMAIL PROTECTED]> wrote:
>
> > Thanks so much Martin.........but I am not trying to validate a date
> > field, I am actually trying to give a dynamic initial value to a text
> > box through struts-config.xml.
> >
> > <form-property name="date" type="java.lang.String"
> > initial="rd.admin.DateFormat.getDate()"/>
>
> >From the DTD, the 'initial' attribute of <form-property> is:
>   "String representation of the initial value for this property."
>
> The typical solution is to pre-populate the form in a "setup" action
> (or in a method of a DispatchAction) before forwarding to the JSP.  Is
> there some reason that won't work for you?
>
> --
> Wendy
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Reply via email to