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
Yup.
That's OK.
I just wondering why the validation is omitted if I define the field as
Integer or int.
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.
Ther
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 have got a strange problem as following:
I would like to use DispatchAction for one of my use case named
customerand 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
4 matches
Mail list logo
