You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by bu...@apache.org on 2003/09/18 19:58:43 UTC
DO NOT REPLY [Bug 23258] New: -
WSDL assigns base64Binary type to hexBinary field
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23258>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23258
WSDL assigns base64Binary type to hexBinary field
Summary: WSDL assigns base64Binary type to hexBinary field
Product: Axis
Version: 1.1
Platform: All
OS/Version: All
Status: NEW
Severity: Normal
Priority: Other
Component: WSDL processing
AssignedTo: axis-dev@ws.apache.org
ReportedBy: LeeKamentsky@comcast.net
I created a java bean (tv.navic.SOAP.Message) that explicitly assigns the XML
types to its properties. I assigned two byte [] fields xsd:hexBinary types so
that I could eyeball the result. The bean correctly serializes and deserializes
in hexBinary, but the WSDL that's generated specifies a type of base64Binary to
the field.
If you look at org.apache.axis.encoding.ser.BeanSerializer at the bottom of the
writeSchema method, you'll see that the calls to writeField do not make use of
non-null XML types. I will include the files to demonstrate the problem, the
generated WSDL and a version of BeanSerializer that reworks the writeField
method slightly to take the overridden XML type into account.