Developmentor Perl / Apache Client problem

[Tony Hong <th...@xmethods.com>]

Sorry if this is a really basic question, but:

I recently ran into a problem where an Apache SOAP client could not
deserialize data being returned from a server implemented using
Developmentor SOAP for Perl.  Developmentor serialized the return variable
as "xsd:integer" .  Running the same method, but forcing a return type
"xsd:int" worked fine.

Is this simply a matter of which form the respective soap teams chose to
support as the "right" encoding description for integers, or is there
something more to this?


The stacktrace generated was as follows:

[SOAPException: faultCode=SOAP-ENV:Client; msg=No Deserializer found to
deserialize a 'http://www.w3.org/1999/XMLSchema:integer' using encoding
style 'http://schemas.xmlsoap.org/soap/encoding/'.;
targetException=java.lang.IllegalArgumentException: No Deserializer found to
deserialize a 'http://www.w3.org/1999/XMLSchema:integer' using encoding
style 'http://schemas.xmlsoap.org/soap/encoding/'.]
        at java.lang.Throwable.<init>(Throwable.java:96)
        at java.lang.Exception.<init>(Exception.java:44)
        at org.apache.soap.SOAPException.<init>(SOAPException.java:71)
        at org.apache.soap.SOAPException.<init>(SOAPException.java:77)
        at org.apache.soap.rpc.Call.invoke(Call.java:181)
        at soapPing.pingHost(soapPing.java:28)
        at soapPing.main(soapPing.java:46)


Thanks - Tony