axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [jira] Updated: (AXIS-1319) WSDL2Java: incorrect handling of xsd:base64Binary?
Date Fri, 16 Apr 2004 17:27:29 GMT
The following issue has been updated:

    Updater: Patrick Peck (
       Date: Fri, 16 Apr 2004 10:25 AM
             Attachment changed to schema-fragment.txt
For a full history of the issue, see:

View the issue:

Here is an overview of the issue:
        Key: AXIS-1319
    Summary: WSDL2Java: incorrect handling of xsd:base64Binary?
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: Axis

   Reporter: Patrick Peck

    Created: Fri, 16 Apr 2004 10:18 AM
    Updated: Fri, 16 Apr 2004 10:25 AM

using the attached schema fragment in a wsdl definition, WSDL2Java generates the attached class. it contains the following methods:

    // Simple Types must have a String constructor
    public CryptoBinary(java.lang.String value) {
        this.value = org.apache.axis.types.HexBinary.decode(value);

    // Simple Types must have a toString for serializing the value
    public java.lang.String toString() {
        return value == null ? null : org.apache.axis.types.HexBinary.encode(value);

since these methods are actually used to (de)serialize the element, the output shows


which is hex encoded (and not base64binary).

This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:

If you want more information on JIRA, or have a bug to report see:

View raw message