Paolo Beccari [EMAIL PROTECTED] wrote:
I suppose this message is always returned when a
conversion error occurs.
Next step is finding a way to hide it. I'll post the
solution, if ever find one.
Dave Newton [EMAIL PROTECTED] wrote:
$ find . -name *.properties | xargs grep -i invalid
Paolo Beccari [EMAIL PROTECTED] wrote:
I suppose this message is always returned when a
conversion error occurs.
Next step is finding a way to hide it. I'll post the
solution, if ever find one.
Dave Newton [EMAIL PROTECTED] wrote:
$ find . -name *.properties | xargs grep -i invalid
--- Paolo Beccari [EMAIL PROTECTED] wrote:
Paolo Beccari [EMAIL PROTECTED] wrote:
I suppose this message is always returned when a
conversion error occurs.
Dave Newton [EMAIL PROTECTED] wrote:
--- Paolo Beccari [EMAIL PROTECTED] wrote:
field-validator type=regex
param name=expression[0-9]/param
message key=requirednumber/
/field-validator
/field
/validators
--- Dave Newton [EMAIL PROTECTED] wrote:
If it's defined as a Long in your action then you
might not be
--- Paolo Beccari [EMAIL PROTECTED] wrote:
field-validator type=regex
param name=expression[0-9]/param
message key=requirednumber/
/field-validator
/field
/validators
If it's defined as a Long in your action then you
might not be able to run a regex on it--I would
param name=expression[0-9]*(\.[0-9]+)?/param
Paolo Beccari wrote:
--- Paolo Beccari [EMAIL PROTECTED] wrote:
field-validator type=regex
param name=expression[0-9]/param
message key=requirednumber/
/field-validator
/field
/validators
--- Dave Newton [EMAIL PROTECTED]
param name=expression[0-9]*(\.[0-9]+)?/param
Hi Lance, as already established (see previous posts), it is not a matter of
regular expressions.
The matter is: the variable in the Action is a Long (and MUST be a Long).
The regex validation does not work, if the variable is not a String.
I'm
Ah... pls ignore
Paolo Beccari wrote:
param name=expression[0-9]*(\.[0-9]+)?/param
Hi Lance, as already established (see previous posts), it is not a
matter of regular expressions.
The matter is: the variable in the Action is a Long (and MUST be a Long).
The regex validation does not
--- Paolo Beccari [EMAIL PROTECTED] wrote:
So how to validate a Long value?
You might just be able to use the conversion
validator.
http://struts.apache.org/2.x/docs/conversion-validator.html
I have not tried this, so I'd be interested in the
results if you do!
Thanks,
Dave
--- Paolo Beccari [EMAIL PROTECTED] wrote:
So how to validate a Long value?
You might just be able to use the conversion
validator.
http://struts.apache.org/2.x/docs/conversion-validator.html
I have not tried this, so I'd be interested in the
results if you do!
Thanks,
Dave
I'm going
Paolo Beccari [EMAIL PROTECTED] wrote:
So how to validate a Long value?
Dave Newton [EMAIL PROTECTED] wrote:
You might just be able to use the conversion
validator.
http://struts.apache.org/2.x/docs/conversion-validator.html
I have not tried this, so I'd be interested in the
results if you
--- Paolo Beccari [EMAIL PROTECTED] wrote:
I suppose this message is always returned when a
conversion error occurs.
Next step is finding a way to hide it. I'll post the
solution, if ever find one.
$ find . -name *.properties | xargs grep -i invalid
Hi all,
I'm a S2 newbie.
Trying to validate input in a *-validation.xml, and found a strange
behaviour:
validators
field name=id
field-validator type=required
message key=required/
/field-validator
field-validator type=regex
!--param
On 5/19/07, Paolo Beccari [EMAIL PROTECTED] wrote:
Hi all,
I'm a S2 newbie.
Trying to validate input in a *-validation.xml, and found a strange
behaviour:
validators
field name=id
field-validator type=required
message key=required/
/field-validator
14 matches
Mail list logo
