Instead of a variable of type "int", that has always a value (the default is 0), you can use the class Integer, that by default is null.
Same with double and Double.
Hope this helps.
 
David
-----Mensaje original-----
De: Liu, Scott [mailto:[EMAIL PROTECTED]
Enviado el: jueves, 15 de julio de 2004 1:07
Para: [EMAIL PROTECTED]
CC: Liu, Scott
Asunto: [castor-user] Why double fields always have default value of 0.0

Hi, All,

 

You may have noticed this or have an explanation. Recently I noticed that even if a client dose not provide any values to double fields I always see “0.0” at the server end in my web services. For example I have a field called “amount” in a sales order transaction and I would like to deny the service if the “amount’ is not provided (for other reasons I have selected to treat the amount as an optional field). I have verified that the xml resulted to send cross the wire did not have any amount element. Now somewhere in the process a default value is added to the “amount” thus I can not reject the transaction based on an empty “amount” field. This also happens on integer fields which have “0” default values.

 

Please share me with your insight and solutions,

 

Thanks,

 

Scott

 

 

*************************************************************
Este correo ha sido procesado por el Antivirus del Grupo FCC.
*************************************************************
*************************************************************
Este correo ha sido procesado por el Antivirus del Grupo FCC
*************************************************************
----------------------------------------------------------- 
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
        unsubscribe castor-user

Reply via email to