G
Gardner Lloyd Bickford III
I have been working with the low level SOAP API in
mozilla/firefox/netscape and I've run into a road block and I am
unsure how to continue or even debug further.
Basically the web service is a javabean running inside of jboss 2.3.7
and axis deals with generating and parsing the SOAP packets. On the
client side I instantiate synchronous SOAPCalls, encode the
parameters, and then invoke the call. This works great for calls that
return simple types such as integers, strings or even arrays of
strings. Unexpected results are returned from any method that returns
complex objects. One example of this is a method that returns an array
of objects. After going through SOAP and getting a value from
SOAPCall.getParameters() all I have is an appropriately size array
with blank strings at every offset.
Using ethereal I was able to verify that the SOAP packets are actually
being returned by the server but for some reason the SOAP API doesn't
seem to decode them properly.
I have read about using schemas to aid in the encoding/decoding
process as well as custom encoders/decoders
http://groups-beta.google.com/group..._doneTitle=Back+to+Search&&d#d4849f79efcbf76c
I am not sure if this may be related to axis producing incompatible
SOAP packets (they work with PHP SOAP) or if I just need to help the
SOAP decoder by giving it more information.
Gardner
mozilla/firefox/netscape and I've run into a road block and I am
unsure how to continue or even debug further.
Basically the web service is a javabean running inside of jboss 2.3.7
and axis deals with generating and parsing the SOAP packets. On the
client side I instantiate synchronous SOAPCalls, encode the
parameters, and then invoke the call. This works great for calls that
return simple types such as integers, strings or even arrays of
strings. Unexpected results are returned from any method that returns
complex objects. One example of this is a method that returns an array
of objects. After going through SOAP and getting a value from
SOAPCall.getParameters() all I have is an appropriately size array
with blank strings at every offset.
Using ethereal I was able to verify that the SOAP packets are actually
being returned by the server but for some reason the SOAP API doesn't
seem to decode them properly.
I have read about using schemas to aid in the encoding/decoding
process as well as custom encoders/decoders
http://groups-beta.google.com/group..._doneTitle=Back+to+Search&&d#d4849f79efcbf76c
I am not sure if this may be related to axis producing incompatible
SOAP packets (they work with PHP SOAP) or if I just need to help the
SOAP decoder by giving it more information.
Gardner