Changes on the validator field-validator required

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

Changes on the validator field-validator required

Greg Huber
We use  <field-validator type="required"> validator to make sure null is
not passed, but if I use a double it does not now validate, it wants a
Double for it to work.

Has there been any changes, or has it always been like this?

also, other validators work ie the min/max below, with the double.

<field name="bean.thePrice">
        <field-validator type="required">
            <message key="bean.theprice.required">unspecified key</message>
        </field-validator>
        <field-validator type="double">
            <param name="minInclusive">0</param>
            <param name="maxInclusive">2999</param>
            <message key="bean.theprice.range">unspecified key</message>
        </field-validator>
</field>

bean:
..
private double thePrice;
public double getThePrice() {
    return thePrice;
}
public void setThePrice(double thePrice) {
    this.thePrice = thePrice;
}
..
Cheers Greg
Reply | Threaded
Open this post in threaded view
|

Re: Changes on the validator field-validator required

Yasser Zamani-2


On 2/23/2018 2:40 PM, Greg Huber wrote:
> We use  <field-validator type="required"> validator to make sure null is
> not passed, but if I use a double it does not now validate, it wants a
> Double for it to work.
>
> Has there been any changes, or has it always been like this?

Did you mean it works in some versions as you expect?

I think the primitive type double, cannot be null at all in java and
automatically will be initialized to 0 by java i.e. you don't need a
null validator in such situations. The non-primitive type Double, can.
This may explain why when you change your type to Double it starts working.

Regards.


---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: Changes on the validator field-validator required

Greg Huber
I checked, and double value comes from ongl,  and yes it wont be a null, so
does not get validated.  I get the struts error though.  I have had to
change all my form beans to be Doubles.
https://struts.apache.org/core-developers/required-validator.html could do
with an update warning no not to use primitives.

Cheers Greg

Cheers Greg

On 23 February 2018 at 12:51, Yasser Zamani <[hidden email]> wrote:

>
>
> On 2/23/2018 2:40 PM, Greg Huber wrote:
> > We use  <field-validator type="required"> validator to make sure null is
> > not passed, but if I use a double it does not now validate, it wants a
> > Double for it to work.
> >
> > Has there been any changes, or has it always been like this?
>
> Did you mean it works in some versions as you expect?
>
> I think the primitive type double, cannot be null at all in java and
> automatically will be initialized to 0 by java i.e. you don't need a
> null validator in such situations. The non-primitive type Double, can.
> This may explain why when you change your type to Double it starts working.
>
> Regards.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
Reply | Threaded
Open this post in threaded view
|

Re: Changes on the validator field-validator required

Yasser Zamani-2
Did your form beans work in previous Struts version and now you have to change all? Or you get this error always with all Struts versions?
On Feb 23, 2018, at 5:48PM, Greg Huber <[hidden email]<mailto:[hidden email]>> wrote:

I checked, and double value comes from ongl,  and yes it wont be a null, so
does not get validated.  I get the struts error though.  I have had to
change all my form beans to be Doubles.
https://struts.apache.org/core-developers/required-validator.html could do
with an update warning no not to use primitives.

Cheers Greg

Cheers Greg

On 23 February 2018 at 12:51, Yasser Zamani <[hidden email]> wrote:



 On 2/23/2018 2:40 PM, Greg Huber wrote:
 We use  <field-validator type="required"> validator to make sure null is
 not passed, but if I use a double it does not now validate, it wants a
 Double for it to work.

 Has there been any changes, or has it always been like this?

 Did you mean it works in some versions as you expect?

 I think the primitive type double, cannot be null at all in java and
 automatically will be initialized to 0 by java i.e. you don't need a
 null validator in such situations. The non-primitive type Double, can.
 This may explain why when you change your type to Double it starts working.

 Regards.


________________________________

 To unsubscribe, e-mail: [hidden email]
 For additional commands, e-mail: [hidden email]


Reply | Threaded
Open this post in threaded view
|

Re: Changes on the validator field-validator required

Greg Huber
Must have worked at some point, otherwise I would not have has the required
in there in the first place.  It was an easy change, so no problem.

Chees Greg

On 23 February 2018 at 16:51, Yasser Zamani <[hidden email]> wrote:

> Did your form beans work in previous Struts version and now you have to
> change all? Or you get this error always with all Struts versions?
> On Feb 23, 2018, at 5:48PM, Greg Huber <[hidden email]<mailto:gr
> [hidden email]>> wrote:
>
> I checked, and double value comes from ongl,  and yes it wont be a null, so
> does not get validated.  I get the struts error though.  I have had to
> change all my form beans to be Doubles.
> https://struts.apache.org/core-developers/required-validator.html could do
> with an update warning no not to use primitives.
>
> Cheers Greg
>
> Cheers Greg
>
> On 23 February 2018 at 12:51, Yasser Zamani <[hidden email]>
> wrote:
>
>
>
>  On 2/23/2018 2:40 PM, Greg Huber wrote:
>  We use  <field-validator type="required"> validator to make sure null is
>  not passed, but if I use a double it does not now validate, it wants a
>  Double for it to work.
>
>  Has there been any changes, or has it always been like this?
>
>  Did you mean it works in some versions as you expect?
>
>  I think the primitive type double, cannot be null at all in java and
>  automatically will be initialized to 0 by java i.e. you don't need a
>  null validator in such situations. The non-primitive type Double, can.
>  This may explain why when you change your type to Double it starts
> working.
>
>  Regards.
>
>
> ________________________________
>
>  To unsubscribe, e-mail: [hidden email]
>  For additional commands, e-mail: [hidden email]
>
>
>