Sorry about that. Forgot to mention that I have recentrly tried this wil 1.1 RC2, and I just tried it again with last nigh't nightly build. Still happens...
The result of this bug is an error in deserialization of incoming boolean values that are xsd:booleans. The Axis-generated classes expect soapenc:boolean's, but get the xsd type. This results in an exception in deserialization. -----Original Message----- From: Davanum Srinivas [mailto:[EMAIL PROTECTED] Sent: Monday, March 24, 2003 11:14 AM To: [EMAIL PROTECTED] Subject: Re: Error in serialization of boolean fields PLEASE try latest nightly build before logging a bug. Thanks, dims --- Michael Ryan <[EMAIL PROTECTED]> wrote: > I have sent the following email to the user group, but have received > no satisfactory response? Should this be entered as a bug? Do any > developers know of a workaround to thi issue? Thanks for your help. > > Mike Ryan > > -----Original Message----- > From: Michael Ryan > Sent: Monday, November 25, 2002 11:26 AM > To: [EMAIL PROTECTED] > Subject: Error in serialization of boolean fields > > > Hello all- > Just started using the released version 1.0 of Axis. I have noticed > that, for complex types, the generated classes are encoding boolean > fields as "soapenc:boolean" instead of as "xsd:boolean". The fields > are defined in the WSDL as "xsd:boolean", but the static field > description blocks are using the wrong namespace. > > Here is a snippet of my WSDL: > <complexType name="FontFlags"> > <complexContent> > <extension base="xsd:anyType"> > <sequence> > <element name="suppressSize" type="xsd:boolean" minOccurs="0" > maxOccurs="1" /> > <element name="suppressColor" type="xsd:boolean" minOccurs="0" > maxOccurs="1" /> > <element name="suppressFace" type="xsd:boolean" minOccurs="0" > maxOccurs="1" /> > </sequence> > </extension> > </complexContent> > </complexType> > > And here is the resulting static block from the FontFlags class: > static { > org.apache.axis.description.FieldDesc field = new > org.apache.axis.description.ElementDesc(); > field.setFieldName("suppressSize"); > field.setXmlName(new javax.xml.namespace.QName("", > "suppressSize")); > field.setXmlType(new > javax.xml.namespace.QName("http://schemas.xmlsoap.org/soap/encoding/";, > "boolean")); > field.setMinOccursIs0(true); > typeDesc.addFieldDesc(field); > field = new org.apache.axis.description.ElementDesc(); > field.setFieldName("suppressColor"); > field.setXmlName(new javax.xml.namespace.QName("", > "suppressColor")); > field.setXmlType(new > javax.xml.namespace.QName("http://schemas.xmlsoap.org/soap/encoding/";, > "boolean")); > field.setMinOccursIs0(true); > typeDesc.addFieldDesc(field); > field = new org.apache.axis.description.ElementDesc(); > field.setFieldName("suppressFace"); > field.setXmlName(new javax.xml.namespace.QName("", > "suppressFace")); > field.setXmlType(new > javax.xml.namespace.QName("http://schemas.xmlsoap.org/soap/encoding/";, > "boolean")); > field.setMinOccursIs0(true); > typeDesc.addFieldDesc(field); > }; > > As you can see, the namespace for the boolean fields is > "http://schemas.xmlsoap.org/soap/encoding/";, when is should be > "http://www.w3.org/2001/XMLSchema";. > > Has anyone else seen this issue, and is there currently a fix for it? > > Michael J. Ryan > Principal Software Engineer > Stellent SCD (Software Components Division) > Chicago, IL > [EMAIL PROTECTED] > > ===== Davanum Srinivas - http://webservices.apache.org/~dims/ __________________________________________________ Do you Yahoo!? Yahoo! Platinum - Watch CBS' NCAA March Madness, live on your desktop! http://platinum.yahoo.com
