The IDE ( eclipse ) does not recognize 0.00 as a valid value for the schema element earlier decalared as double with minInclusive value of 0.00. I have seen few articles on the net which talk about the conversion problems with 0, 0.00, 0.0000 etc all are not considered to be zeros. Another problem as i had earlier stated is AXIS does not genereted the conditions properly to check for the minInclusive value stated in the schema. It puts a condition to check for something greater.
-----Original Message----- From: Amila Suriarachchi [mailto:[EMAIL PROTECTED] Sent: 05 September 2007 05:36 To: [email protected] Subject: Re: On ADB Binding what is the exception you are getting? here is the setter method generated public void setGEM_PostvDbl_Type(double param) { if (org.apache.axis2.databinding.utils.ConverterUtil.compare(param, "0.00 ") > 0) { this.localGEM_PostvDbl_Type = param; } else { throw new java.lang.RuntimeException(); } } and this calls ConverterUtil.compare method. public static double compare(double doubleValue, String value) { return doubleValue - Double.parseDouble(value); } so it basically use the parseDouble method of the Double class. Amila. On 9/4/07, Gudla, Natraj (GE Money, consultant) < [EMAIL PROTECTED]> wrote: I am just running through another problem with min inclusive values on double types. For declaration, <xsd:simpleType name="GEM_PostvDbl_Type" > <xsd:restriction base="xsd:double" > <xsd:minExclusive value= "0.00"/> </xsd:restriction> </xsd:simpleType> An xml schema instance value of 0.00 throws an error, saying it not a valid value. 0.00 is a double value, and what could be the problem? Thanks Natraj -----Original Message----- From: Amila Suriarachchi [mailto: [EMAIL PROTECTED] Sent: 04 September 2007 13:07 To: [email protected] Subject: Re: On ADB Binding On 9/4/07, Gudla, Natraj (GE Money, consultant) < [EMAIL PROTECTED]> wrote: Hi, I am using AXIS2 1.2, Generated the data binding classes using WSDL2Java utility and i am trying to parse instance of an xml against the generated binding classes. I see a problem in which the xml restrictions are converted into code by AXIS utility. My XML schema condition : <!-- Positive Integer simple type --> <xsd:simpleType name="GEM_PostvInt_Type" > <xsd:restriction base="xsd:integer" > <xsd:minExclusive value="0" /> </xsd:restriction> </xsd:simpleType> The corresponding code generated in a class : /** * Auto generated setter method * * @param param * GEM_PostvInt_Type */ public void setGEM_PostvInt_Type(java.math.BigInteger param) { if (org.apache.axis2.databinding.utils.ConverterUtil.compare(param, "0") > 0) { this.localGEM_PostvInt_Type = param; } else { throw new java.lang.RuntimeException(); } } I check the api docs for ConverterUtil, which says this particular method returns a zero when values are equal, +ve when greater, -ve when lesser. If you look at my xml, i want zero to be mininclusive your given schema part declares it as <xsd:minExclusive value="0" /> Anyway if you don't have any special reason to use Axis2 1.2 better switch to Axis2 1.3. Amila. meaning it should be allowed, in such a case why is the method checking for >0 and not >=0. I get an exception, as the control moves to the else part. i see the converterutil returns a 0 as input value is zerp and is being compared with zero. Thanks Natraj -----Original Message----- From: Gudla, Natraj (GE Money, consultant) Sent: 30 August 2007 11:48 To: ' [email protected]' Cc: ' <mailto:[EMAIL PROTECTED]> [EMAIL PROTECTED]' Subject: RE: On ADB Binding Thanks Amila, It clarifies my doubt. We were a bit hesitant to go ahead with the ADB binding for the reasons on limitations stated in the documents. -----Original Message----- From: Amila Suriarachchi [mailto: [EMAIL PROTECTED] Sent: 30 August 2007 11:44 To: [email protected] Subject: Re: On ADB Binding ADB does support restrictions and extensions. those documentation are bit obsolete. Amila. On 8/30/07, Gudla, Natraj (GE Money, consultant) < [EMAIL PROTECTED]> wrote: Hi, The AXIS2 1.2 documentation states the ADB binding does not support xml restrictions and extensions. Is it really true? When i generated Java classes from a WSDL, i see the restrictions on the types to be properly generated within the element classes. Following is part of my schema with restriction on the max length. <xsd:simpleType name="LN_PaymentProtection"> <xsd:annotation> <xsd:documentation>Elements of payment protection represent the protection types and can be only a string type</xsd:documentation> </xsd:annotation> <xsd:restriction base="xsd:string"> <xsd:maxLength value="2"></xsd:maxLength> </xsd:restriction> </xsd:simpleType> The code generated by AXIS ADB binding through WSDL2Java, check on the max length within the code. public void setLN_PaymentProtection( java.lang.String param) { if ((java.lang.String.valueOf(param).length() <= 2)) { this.localLN_PaymentProtection = param; } else { throw new java.lang.RuntimeException(); } } Do you see a point over here? what did the documentation exactly mean? Thanks Natraj. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> -- Amila Suriarachchi, WSO2 Inc. -- Amila Suriarachchi, WSO2 Inc. -- Amila Suriarachchi, WSO2 Inc.
