|
Sekhar, Based
on the documentation, it looks like there is a bug in wsdl2java. Have you been able to map a nillable
xsd:int to a Java Integer? Has anyone
else? Bill Bill Heitzeg 1-734-995-9131 -----Original
Message----- Here is the documentation on this from
user guide If the WSDL says that an object can be
nillable, that is the caller may choose to return a value of nil, then the
primitive data types are replaced by their wrapper classes, such as Byte,
Double, Boolean, etc. ----------------------------------------------- This means that the your wsdl is saying
that it is actually mapped to Integer. Sekhar -----Original Message----- Thanks Matt, Unfortunately, the WSDL does specify that
the element is nillable, but it is still being mapped to an int. In the
wsdl the element looks like: <element name="sailMinLenDays"
nillable="true" type="xsd:int" /> Bill Bill Heitzeg -----Original Message----- I believe that if the WSDL specifies that
the field is nillable, then Matt Hi, Thanks, Bill Bill Heitzeg
|
Title: RE: wsdl2java mapping primitives to objects
- wsdl2java mapping primitives to objects Heitzeg, Bill
- Re: wsdl2java mapping primitives to objects Matthew Sgarlata
- RE: wsdl2java mapping primitives to objects Heitzeg, Bill
- RE: wsdl2java mapping primitives to objects Mallipeddi, Sekhar
- Re: wsdl2java mapping primitives to objects Heitzeg, Bill
- Re: wsdl2java mapping primitives to objects Matthew Sgarlata
- RE: wsdl2java mapping primitives to objects Mallipeddi, Sekhar
- RE: wsdl2java mapping primitives to objects Heitzeg, Bill
- RE: wsdl2java mapping primitives to objects Heitzeg, Bill
- RE: wsdl2java mapping primitives to objects Richard Martin
