Yes, I authored the (attached) WSDL and delivered it to our partner to implement. Axis uses the WSDL just fine with the exception of the enumerated types, so I am not using them. I am not familiar with either WebMethods or SAP and know little about their implementation. I'm trying to work with them, but its rather difficult since they are in Australia and I'm in the US.
Thanks, Russ -----Original Message----- From: Chen, Shuyuan [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 29, 2004 3:30 PM To: [EMAIL PROTECTED] Subject: RE: SAP interop problem with RPC Russ, The exception is actually coming from WebMethods. I supposed you are calling WebMethods Web Services that in turn calling SAP backend system. Do you have the WSDL file? Regards! -----Original Message----- From: Pridemore, Russell (MAN-Corporate) [mailto:[EMAIL PROTECTED] Sent: Wednesday, Sep 29, 2004 12:19 PM To: '[EMAIL PROTECTED]' Subject: SAP interop problem with RPC Hello all. I have implemented & tested an application using Axis 1.1. It is fairly simple, only requiring a request/response pattern using simple types. However, now I'm trying to integrate with an SAP backend system and I'm running into issues. (SAP is the web service and Axis is the client). Calls to SAP result in: faultDetail: {http://www.webMethods.com/2001/10/soap/encoding}exception: <ns1:className>com.wm.soap.coder.SoapCoderRuntimeException</ns1:className> <ns1:message xml:lang="en-AU" xmlns:xml="http://www.w3.org/XML/1998/namespace";>[B2BCORE.0076.9201] SOAP Message Coder cannot decode message; no encoding style is specified</ns1:message> I've looked through the Axis documentation and found references to encodingStyle on Call objects. Do I need to set the encodingStyle on the Call? Isn't this an optional attribute? Any suggestions would be greatly appreciated. Thanks, Russ
simulcast.wsdl
Description: Binary data
