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 2002/09/11 16:54:33 UTC
DO NOT REPLY [Bug 12537] New: -
Possible Erroneous Bad Type Exception on Client
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=12537>.
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=12537
Possible Erroneous Bad Type Exception on Client
Summary: Possible Erroneous Bad Type Exception on Client
Product: Axis
Version: current (nightly)
Platform: PC
OS/Version: Windows XP
Status: NEW
Severity: Normal
Priority: Other
Component: Serialization/Deserialization
AssignedTo: axis-dev@xml.apache.org
ReportedBy: andrea.dick@ca.com
I have an RPC style web service defined to return data of type Object. The web
service works fine returning Strings, arrays of Strings, array's of Integers as
well as my own java object's. The web service is failing when I return an
Integer, a Long or a Byte. Using TCPMon I can see that the Web Service is able
to format and return the data without a problem. However, the client side code
is causing the following exception prior to returning the data to my client
program. (Exception: Remote Exception caught: org.xml.sax.SAXException: Bad
types (byte -> class java.lang.Object)".