axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pridemore, Russell (MAN-Corporate)" <>
Subject RE: SAP interop problem with RPC
Date Wed, 29 Sep 2004 22:03:03 GMT
I started with the WSDL and generated skeleton/stub from that using
Axis' tool.  I was just looking at the generated code, wondering if
there was any way to modify it to SAP's liking.


-----Original Message-----
From: Anne Thomas Manes []
Sent: Wednesday, September 29, 2004 5:56 PM
Subject: RE: SAP interop problem with RPC

The encoding style attribute is required when using RPC/encoded.
Have you tried generating a stub from the WSDL rather than using the Call


-----Original Message-----
From: Pridemore, Russell (MAN-Corporate) [] 
Sent: Wednesday, September 29, 2004 9:19 PM
To: ''
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:
<ns1:message xml:lang="en-AU"
xmlns:xml="">[B2BCORE.0076.9201] SOAP
Message Coder cannot decode message; no encoding style is

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


View raw message