Ted Husted wrote:
> It looks right to me, David (and welcome back, BTW).
Me too, and thanks.
> Maybe we need to add a test case to the validator sample app to be
> sure everything is still working as advertised.
That's probably a good idea. I think it needs some rigorous testing;
I've run in
Thanks for the suggestion, but that didn't work either.
It's strange because I'm validating other fields in the same form and
the error messages are correct for those fields. Also, If I change the
range message in the resource bundle, that change is reflected in the
message, but it always disp
David, should you be adding the as I have below AND, shouldn't
login.number.displayName=Number be login.number.displayName=number?
At 08:40 AM 8/30/2002 -0600, you wrote:
>Sorry to repost this, but it got buried in a bunch of biere messages
>yesterday...
>
>I'm trying to validate a range
Should:
login.number.displayName=Number
be:
login.number.displayName=number
?
At 08:40 AM 8/30/2002 -0600, you wrote:
>Sorry to repost this, but it got buried in a bunch of biere messages
>yesterday...
>
>I'm trying to validate a range using the validator. I've got this in
>valid
It looks right to me, David (and welcome back, BTW).
Maybe we need to add a test case to the validator sample app to be sure
everything is still working as advertised.
Are you using beta 2 or what?
-Ted.
David Geary wrote:
> Sorry to repost this, but it got buried in a bunch of biere message
Sorry to repost this, but it got buried in a bunch of biere messages
yesterday...
I'm trying to validate a range using the validator. I've got this in
validation.xml...
min
I'm trying to validate a range using the validator. I've got this in
validation.xml...
min
5
max
7 matches
Mail list logo
