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 ji...@apache.org on 2004/04/16 19:19:29 UTC
[jira] Created: (AXIS-1319) WSDL2Java: incorrect handling of xsd:base64Binary?
Message:
A new issue has been created in JIRA.
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/AXIS-1319
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
Versions:
1.1
Assignee:
Reporter: Patrick Peck
Created: Fri, 16 Apr 2004 10:18 AM
Updated: Fri, 16 Apr 2004 10:18 AM
Description:
using the attached schema fragment in a wsdl definition, WSDL2Java generates the attached CryptoBinary.java 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
<ns3:RSAKeyValue>
<ns3:Modulus>6162636465666731323334353132333435e4f6e4f6fc</ns3:Modulus>
<ns3:Exponent>3132333435</ns3:Exponent>
</ns3:RSAKeyValue>
which is hex encoded (and not base64binary).
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Closed: (AXIS-1319) WSDL2Java: incorrect handling of xsd:base64Binary?
Posted by ji...@apache.org.
Message:
The following issue has been closed.
Resolver: Davanum Srinivas
Date: Sun, 18 Apr 2004 2:29 PM
Has been fixed in 1.2 Beta.
thanks,
dims
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/AXIS-1319
Here is an overview of the issue:
---------------------------------------------------------------------
Key: AXIS-1319
Summary: WSDL2Java: incorrect handling of xsd:base64Binary?
Type: Bug
Status: Closed
Priority: Major
Resolution: FIXED
Project: Axis
Fix Fors:
current (nightly)
Versions:
1.1
Assignee:
Reporter: Patrick Peck
Created: Fri, 16 Apr 2004 10:18 AM
Updated: Sun, 18 Apr 2004 2:29 PM
Description:
using the attached schema fragment in a wsdl definition, WSDL2Java generates the attached CryptoBinary.java 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
<ns3:RSAKeyValue>
<ns3:Modulus>6162636465666731323334353132333435e4f6e4f6fc</ns3:Modulus>
<ns3:Exponent>3132333435</ns3:Exponent>
</ns3:RSAKeyValue>
which is hex encoded (and not base64binary).
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Commented: (AXIS-1319) WSDL2Java: incorrect handling of xsd:base64Binary?
Posted by ji...@apache.org.
The following comment has been added to this issue:
Author: Davanum Srinivas
Created: Fri, 16 Apr 2004 10:25 AM
Body:
can you please attach your complete WSDL?
thanks,
dims
---------------------------------------------------------------------
View this comment:
http://issues.apache.org/jira/browse/AXIS-1319?page=comments#action_35077
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/AXIS-1319
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
Versions:
1.1
Assignee:
Reporter: Patrick Peck
Created: Fri, 16 Apr 2004 10:18 AM
Updated: Fri, 16 Apr 2004 10:25 AM
Description:
using the attached schema fragment in a wsdl definition, WSDL2Java generates the attached CryptoBinary.java 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
<ns3:RSAKeyValue>
<ns3:Modulus>6162636465666731323334353132333435e4f6e4f6fc</ns3:Modulus>
<ns3:Exponent>3132333435</ns3:Exponent>
</ns3:RSAKeyValue>
which is hex encoded (and not base64binary).
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Updated: (AXIS-1319) WSDL2Java: incorrect handling of xsd:base64Binary?
Posted by ji...@apache.org.
The following issue has been updated:
Updater: Patrick Peck (mailto:patrick@zync.at)
Date: Fri, 16 Apr 2004 10:25 AM
Changes:
Attachment changed to schema-fragment.txt
---------------------------------------------------------------------
For a full history of the issue, see:
http://issues.apache.org/jira/browse/AXIS-1319?page=history
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/AXIS-1319
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
Versions:
1.1
Assignee:
Reporter: Patrick Peck
Created: Fri, 16 Apr 2004 10:18 AM
Updated: Fri, 16 Apr 2004 10:25 AM
Description:
using the attached schema fragment in a wsdl definition, WSDL2Java generates the attached CryptoBinary.java 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
<ns3:RSAKeyValue>
<ns3:Modulus>6162636465666731323334353132333435e4f6e4f6fc</ns3:Modulus>
<ns3:Exponent>3132333435</ns3:Exponent>
</ns3:RSAKeyValue>
which is hex encoded (and not base64binary).
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Updated: (AXIS-1319) WSDL2Java: incorrect handling of xsd:base64Binary?
Posted by ji...@apache.org.
The following issue has been updated:
Updater: Patrick Peck (mailto:patrick@zync.at)
Date: Fri, 16 Apr 2004 10:21 AM
Changes:
Attachment changed to CryptoBinary.java
---------------------------------------------------------------------
For a full history of the issue, see:
http://issues.apache.org/jira/browse/AXIS-1319?page=history
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/AXIS-1319
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
Versions:
1.1
Assignee:
Reporter: Patrick Peck
Created: Fri, 16 Apr 2004 10:18 AM
Updated: Fri, 16 Apr 2004 10:21 AM
Description:
using the attached schema fragment in a wsdl definition, WSDL2Java generates the attached CryptoBinary.java 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
<ns3:RSAKeyValue>
<ns3:Modulus>6162636465666731323334353132333435e4f6e4f6fc</ns3:Modulus>
<ns3:Exponent>3132333435</ns3:Exponent>
</ns3:RSAKeyValue>
which is hex encoded (and not base64binary).
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Updated: (AXIS-1319) WSDL2Java: incorrect handling of xsd:base64Binary?
Posted by ax...@ws.apache.org.
The following issue has been updated:
Updater: Steve Green (mailto:steve.green@epok.net)
Date: Tue, 31 Aug 2004 8:19 AM
Comment:
This is a new patch for the same problem. This patch is fixed to account for changes in the code base.
Changes:
Attachment changed to new_base64.patch
---------------------------------------------------------------------
For a full history of the issue, see:
http://issues.apache.org/jira/browse/AXIS-1319?page=history
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/AXIS-1319
Here is an overview of the issue:
---------------------------------------------------------------------
Key: AXIS-1319
Summary: WSDL2Java: incorrect handling of xsd:base64Binary?
Type: Bug
Status: Reopened
Priority: Major
Project: Axis
Fix Fors:
current (nightly)
Versions:
1.1
Assignee: Davanum Srinivas
Reporter: Patrick Peck
Created: Fri, 16 Apr 2004 10:18 AM
Updated: Tue, 31 Aug 2004 8:19 AM
Description:
using the attached schema fragment in a wsdl definition, WSDL2Java generates the attached CryptoBinary.java 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
<ns3:RSAKeyValue>
<ns3:Modulus>6162636465666731323334353132333435e4f6e4f6fc</ns3:Modulus>
<ns3:Exponent>3132333435</ns3:Exponent>
</ns3:RSAKeyValue>
which is hex encoded (and not base64binary).
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Updated: (AXIS-1319) WSDL2Java: incorrect handling of xsd:base64Binary?
Posted by ji...@apache.org.
The following issue has been updated:
Updater: Patrick Peck (mailto:patrick@zync.at)
Date: Fri, 16 Apr 2004 10:27 AM
Comment:
attached complete wsdl
Changes:
Attachment changed to szr.wsdl
---------------------------------------------------------------------
For a full history of the issue, see:
http://issues.apache.org/jira/browse/AXIS-1319?page=history
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/AXIS-1319
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
Versions:
1.1
Assignee:
Reporter: Patrick Peck
Created: Fri, 16 Apr 2004 10:18 AM
Updated: Fri, 16 Apr 2004 10:27 AM
Description:
using the attached schema fragment in a wsdl definition, WSDL2Java generates the attached CryptoBinary.java 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
<ns3:RSAKeyValue>
<ns3:Modulus>6162636465666731323334353132333435e4f6e4f6fc</ns3:Modulus>
<ns3:Exponent>3132333435</ns3:Exponent>
</ns3:RSAKeyValue>
which is hex encoded (and not base64binary).
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Closed: (AXIS-1319) WSDL2Java: incorrect handling of xsd:base64Binary?
Posted by ax...@ws.apache.org.
Message:
The following issue has been closed.
Resolver: Davanum Srinivas
Date: Thu, 2 Sep 2004 5:18 AM
Fixed.
thanks,
dims
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/AXIS-1319
Here is an overview of the issue:
---------------------------------------------------------------------
Key: AXIS-1319
Summary: WSDL2Java: incorrect handling of xsd:base64Binary?
Type: Bug
Status: Closed
Priority: Major
Resolution: FIXED
Project: Axis
Fix Fors:
current (nightly)
Versions:
1.1
Assignee: Davanum Srinivas
Reporter: Patrick Peck
Created: Fri, 16 Apr 2004 10:18 AM
Updated: Thu, 2 Sep 2004 5:18 AM
Description:
using the attached schema fragment in a wsdl definition, WSDL2Java generates the attached CryptoBinary.java 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
<ns3:RSAKeyValue>
<ns3:Modulus>6162636465666731323334353132333435e4f6e4f6fc</ns3:Modulus>
<ns3:Exponent>3132333435</ns3:Exponent>
</ns3:RSAKeyValue>
which is hex encoded (and not base64binary).
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Updated: (AXIS-1319) WSDL2Java: incorrect handling of xsd:base64Binary?
Posted by ji...@apache.org.
The following issue has been updated:
Updater: Patrick Peck (mailto:patrick@zync.at)
Date: Fri, 16 Apr 2004 10:33 AM
Comment:
you will also need this one
Changes:
Attachment changed to pvp_17.xsd
---------------------------------------------------------------------
For a full history of the issue, see:
http://issues.apache.org/jira/browse/AXIS-1319?page=history
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/AXIS-1319
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
Versions:
1.1
Assignee:
Reporter: Patrick Peck
Created: Fri, 16 Apr 2004 10:18 AM
Updated: Fri, 16 Apr 2004 10:33 AM
Description:
using the attached schema fragment in a wsdl definition, WSDL2Java generates the attached CryptoBinary.java 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
<ns3:RSAKeyValue>
<ns3:Modulus>6162636465666731323334353132333435e4f6e4f6fc</ns3:Modulus>
<ns3:Exponent>3132333435</ns3:Exponent>
</ns3:RSAKeyValue>
which is hex encoded (and not base64binary).
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira