M.Liang Liu wrote:
Yup.
That's OK.
I just wondering why the validation is omitted if I define the field as
Integer or int.
Perhaps because an integer-typed field can only hold an integer value,
so the 'integer' validation rule is always going to pass.
L.
Defining all the fields as String may be a general way .
Thanks.
On 6/4/06, M.Liang Liu <[EMAIL PROTECTED]> wrote:
I test the " integer " depends and it works well in a single page.
There must be something to do with the setCoustomer.do.
I am trying to define the field as String ,NOT Integer.
Just waiting...
On 6/4/06, M.Liang Liu <[EMAIL PROTECTED]> wrote:
>
> I have got a strange problem as following:
> I would like to use DispatchAction for one of my use case named
> customer and I create a setCustomer.do action to init the hidden
> property---methodToCall.
> Then that action execute method returns mapping.findFordward
> ("continue");
>
> The continue page makes use of the same ActionForm as setCustomer.do.
>
> There is an <html:text> fields which should be required,integer in the
> next page(namely continued page).
>
> however,no validation for that property and it would be 0 if other
> fields fails.
>
> Required,date for other fields are just OK.But the integer validation
> can NOT work as expected.
>
> p.s If I put a string not integer to that field,it would be 0 in the
> end.
>
> Any advice?
>
>
> The problem are strange to me and I want to know the solution.
>
> Thanks for reading and looking forward to u.
> --
> Why Signature?
>
--
Why Signature?
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
