RPC/encoded style

Hi Experts,
I have read it in some forum thread stating that, we can't use RPC/encoded style in XI. Even if we get RPC style wsdl files from other platforms we have to first convert it into Document style to access XI.
Question:
When we create wsdl thro' XI also, it automatically creates with document style. Do we have any option to create a wsdl file with RPC style? If it is not possible with XI then, is there any other way to create RPC style wsdl file for the XI service.
Regards
Sara

Yes its possible,
Please check following :-
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/c018da90-0201-0010-ed85-d714ff7b7019
RPC WSDL in XI
Vishal
Reward points for useful Help

Similar Messages

How to handle rpc/encoded style messages using BizTalk?

I am integrating with a lot of services and one of our customers has a service with rpc/encoded style
I could consume and generate schema from their wsdl file via BizTalk consume WCF wizard.
Once I am trying to call the service with request message that generated from the schema, it is giving an error that can not desterilize the first element of the message.
No Deserializer found to deserialize a 'FieldName' using encoding style 'null'
I compared the stub xml request message from SaopUI and I noticed that the xml expecting the data type with the element like this .
<soapenv:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsb="WSBanka">
<soapenv:Header/>
<soapenv:Body>
<wsb:bnkBorcsorgulama soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<sozlesmeNo xsi:type="xsd:string">?</sozlesmeNo>
<bankaKodu xsi:type="xsd:string">?</bankaKodu>
<anahtar xsi:type="xsd:string">?</anahtar>
</wsb:bnkBorcsorgulama>
</soapenv:Body>
</soapenv:Envelope>
On the other hand, I got the request of the message from Fiddler using the BizTalk , and the generate xml of the BizTalk schema without the data type.
<soapenv:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsb="WSBanka">
<soapenv:Header/>
<soapenv:Body>
<wsb:bnkBorcsorgulama>
<sozlesmeNo>?</sozlesmeNo>
<bankaKodu>?</bankaKodu>
<anahtar>?</anahtar>
</wsb:bnkBorcsorgulama>
</soapenv:Body>
</soapenv:Envelope>
In SoapUi, if I remove a datatype from the message, I will get same error from the BizTalk request.
I read some articles that rpc/encoded style are not supported but I am not sure and these articles are not clear.
I also read that it was supported with Soap adapter but now it is deprecated.
So, Is there any one has an experience in rpc/encoded style messages and how to handle these message in BizTalk or is there any work around to handle these messages?
Your inputs really appreciate it.
Thanks in advance,
When you see answers and helpful posts, please click Vote As Helpful, Propose As Answer, and/or Mark As Answer

Hi,
Please refer to the document which might help you:
#RPC/Encoded Style
http://www.c-sharpcorner.com/UploadFile/martinkropp/DesigningInteroperableWebService11232005044847AM/DesigningInteroperableWebService.aspx

RPC/encoded style webservice

Hi Experts,
How to expose RPC/encoded style webservices from XI? As far as I know, we can expose Document literal style webservice from PI7.0.
Could you please tell me, for this question where I can get the exact answer?
Regards
Sara

Hi,
please go through below links
Using XML-RPC in NetWeaver
/people/sap.user72/blog/2004/09/23/using-xml-rpc-in-netweaver
External Data Loads for CRM 4.0 using XIF adapter
/people/stephen.johannes/blog/2005/08/18/external-data-loads-for-crm-40-using-xif-adapter
XML-RPC protocol and XIF Adapter
XML-RPC protocol and XIF Adapter
Thanks
Swarup

What is the general way to invoke a rpc/encoded webservice?

Hi,
I have some confusion in invoking webservices, ok, let me explain my question in detail:
Usually, we access a web service througt its wsdl file, for a rpc/encoded style, for example, in Axis enviroment, I will need the java object for the complex message types, how can I get these java files? If I use the Sun provided WSDP tool to compile the wsdl file and get these java files, do they work? If I am not in the Axis enviroment, maybe I will compose the SOAP request directly, so, what is the general way?
Thanks.

Hello,
When you want to invoke a Web Services (RPC or Document style) you generally as you said create a set fo Java class to: map the messages information to Java code, and create a proxy/stub to do the call.
Using Oracle Application Server Web Service framework you have several way of creating this client classes:
- using Oracle JDeveloper just do a File>New>Web Services>Web Service Proxy
- using the command line tool, and associated Ant tasks (WSA:Web Service Assembler), see the Web Services Developer Guide
Regards
Tugdual Grall

Supports ORACLE PM RPC/encoded ?

Hello !
Is it possible, that the Process Manager can't handle RPC/encoded style ?
Axis send multirefs, when RPC/encoded style is used by webservices ! The ORACLE PM can't handle multirefs. Is a webservice send a message to a BPEL process, deployed on a oracle PM, and the message from the webservice contains multirefs, the Oracle PM gives a fault like NullPointerException !
Have anybody similar experiences ? Is it posible to configure the Oracle PM handle multiref or RPC/encoded style correct ?
Thanks

I have a bug logged against this issue, bug # is 5990259. However, the service I was calling is no longer available, so development can't reproduce it... If you gave them your example as well maybe they could progress this bug? Anyway BPEL does work with RPC/Encoded, it just doesn't like those multi refs. The company we were interacting with was using WebObjects, which was behaving exactly as in your example, and they changed an option on the web service to get rid of the multi refs and it worked (was still RPC/Encoded).

J2ME + message style "rpc/encoding"

Hi,
I have a web services with message style "rpc/encoded" and i need consume this web service from a J2ME app. I wrote in the J2ME help that is impossible because it supports the "document/literal" style. How can i call this methods? Is it possible?
Thanks.
Bruno

Rajesh -
Thanks, that is what I was looking for. Do you know if the sample client
code follows JAX-RPC? Or is this special API developed for Workshop web
services?
Thanks,
Pat
"Rajesh Mirchandani" <[email protected]> wrote in message
news:[email protected]..
If you look into the test view you will find a link for a java proxy(click the
"overview" tab and the the "Java Proxy" tab.). If you copy and paste thatcode
into a java client or a servlet you should be able to invoke the webservice.
>
Let me know if you need an example.
Pat Regan wrote:
It seems to me that, under the hood, a session bean is always the first
component called in a Workshop created web service. If this is the
case,
then would a Java client always use the JAX-RPC api to call it? Evenfor an
asynchronous web service? Does anyone have an example Java Client that
invokes a Workshop created web service?
Thanks,
Pat--
Rajesh Mirchandani
Developer Relations Engineer
BEA Support

Use of RPC-Encoding service style in PSFT Integration Broker

It appears that in PT 8.46, the only service style supported for integration is RPC-Encoding. Can someone confirm this for me? This is an outdated standard, not supported by the WS-I, and not in WSDL2. I'm wondering why this was used, if there's an option to configure it to use Document Literal instead, or to see if later versions of PeopleTools support more service styles.
Thanks.

Hi,
PeopleSoft Integration Broker generates WSDLs which conforms to WSDL 1.1. PeopleSoft supports document style.
I am able to generate Document style WSDLs in both 8.46 and 8.48 PeopleTools version. Please see below:
PeopleTools 8.46
<wsdl:binding name="CUSTOMER_SYNCBinding" type="wsdl_target:CUSTOMER_SYNC">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http" />
<wsdl:operation name="CUSTOMER_SYNCSoapIn">
<soap:operation style="document" soapAction="CUSTOMER_SYNCSoapIn" />
PeopleTools 8.48
<wsdl:binding name="DEPT_SYNC_Binding" type="tns:DEPT_SYNC_PortType">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="DEPT_SYNC">
How did you generate your WSDL?
-Siva

Problem with RPC/encoded WSDL

I'm having trouble calling a web service that is based on an RPC-encoded WSDL. I've already made slight changes to the WSDL, so that I get a work-able message type for mapping purposes. These changes are based on <a href="http://www.ws-i.org/Profiles/BasicProfile-1.0-2004-04-16.html#refinement16556272"><b>soapenc:Array</b> recommendations in WSDL 1.1 Section 2.2</a> for declaration of array types.
Here's a snippet of the WSDL:
<wsdl:definitions ...>
<wsdl:types>
    <schema ...>
      <complexType name="ArrayOf_tns1_ServiceOption">
        <complexContent>
          <restriction base="soapenc:Array">
            <attribute ref="soapenc:arrayType"
              wsdl:arrayType="tns1:ServiceOption[]"
              xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"/>
          </restriction>
        </complexContent>
      </complexType>
    </schema>
    <schema ...>
      <complexType name="ServiceOption">
        <sequence>
          <element name="key" nillable="true"
                    type="xsd:string"/>
          <element name="value" nillable="true"
                    type="xsd:string"/>
        </sequence>
      </complexType>
    </schema>
</wsdl:types>
</wsdl:definitions>
I've changed it to:
<wsdl:definitions ...>
<wsdl:types>
    <schema ...>
      <complexType name="ArrayOf_tns1_ServiceOption">
        <sequence>
          <element name="ServiceOption"
                    type="tns1:ServiceOption"
                    minOccurs="0" maxOccurs="unbounded"/>
        </sequence>
      </complexType>
    </schema>
    </schema>
    <schema ...>
      <complexType name="ServiceOption">
        <sequence>
          <element name="key" nillable="true"
                    type="xsd:string"/>
          <element name="value" nillable="true"
                    type="xsd:string"/>
        </sequence>
      </complexType>
    </schema>
</wsdl:types>
</wsdl:definitions>
The above changes have allowed me to make message mappings. But the I still get an error when sending a request to the web service. It seems that it requires the <b>xsi:type</b> and <b>soapenc:arrayType</b> attributes for arrays.
<b>How can I create these attributes? How does XI handle RPC-encoded WSDLs?</b> I haven't encountered these problems with document-literal WSDLs.
Thanks in advance.

Hi Lorenzo,
the extended support of rpc-style does <b>not</b> include the support of soapenc:array. It just addresses the root of the message and its direct children (as discussed in the thread where I added this hint).
In the documentation of External Definitions you can find a hint where to find a list of supported XSD/DTD/WSDL-features. However, also there you will find no hint on the fact that soapenc:array is not supported. The reason for this is, that soapenc:array is specified in none of these standards. It is some artifact that SOAP smuggled into XSD. For good reasons WS-I prohibits the use of this artifact.
Hence, if you need support for argumentation I can only point out the WS-I document I already linked.
Greetings
Stephan

Web Service Client encoding style error

Hi all,
I have a created a java static stub client (created with wscompile from the wsdp). If I run the client I receive the following error
"unexpected encoding style: expected=http://schemas.xmlsoap.org/soap/encoding/..."
I am using a delphi web service server, the encoding style is set to "http://schemas.xmlsoap.org/soap/encoding/"
My server simply echos a string with the method name "echoString"
Where do I go from here?
Does the xmlns tag in the "config-wsdl.xml" have anything to do with it?
Complete error :
java.rmi.RemoteException: Runtime exception; nested exception is:
unexpected encoding style: expected=http://schemas.xmlsoap.org/soap/encoding/, actual=
at com.sun.xml.rpc.client.StreamingSender._handleRuntimeExceptionInSend(StreamingSender.java:248)
at com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.java:230)
at staticstub.IMyEmailWebService_Stub.echoString(IMyEmailWebService_Stub.java:68)
at DelphiClass.main(DelphiClass.java:25)
Caused by: unexpected encoding style: expected=http://schemas.xmlsoap.org/soap/encoding/, actual=
at com.sun.xml.rpc.encoding.SOAPDeserializationContext.verifyEncodingStyle(SOAPDeserializationContext.java:159)
at com.sun.xml.rpc.encoding.ObjectSerializerBase.deserialize(ObjectSerializerBase.java:150)
at com.sun.xml.rpc.encoding.ReferenceableSerializerImpl.deserialize(ReferenceableSerializerImpl.java:134)
at staticstub.IMyEmailWebService_Stub._deserialize_echoString(IMyEmailWebService_Stub.java:173)
at staticstub.IMyEmailWebService_Stub._readFirstBodyElement(IMyEmailWebService_Stub.java:157)
at com.sun.xml.rpc.client.StreamingSender._send(StreamingSender.java:158)
Thank you in advance
Garth

Looks like the server is not using the correct encoding. I suggest using a packet sniffer so you can actually see the SOAP message to verify that. Apache Axis has a tcpmon utility that works very nicely.

Unexpected encoding style

Hi all. I'm new to Oracle and Web Services in general, so do pardon me in advance.
I followed the example here: http://www.oracle.com/technology/obe/obe1013jdev/ws/wsandascontrol.htm and deployed the web service to the external OC4J server.
Subsequently, I tried calling the web service using the OmniPortlet in OracleAS but it gives this error:
Call to Web Service Failed. [env:Client : caught exception while handling request: unexpected encoding style: expected=, actual=http://xml.apache.org/xml-soap/literalxml]
Any help is appreciated.

Jose,
When you work with Web Services, the common development flow is as follow:
1) develop your service endpoint. You can start from JAVA code or PL/SQL package (bottom-up) or from a WSDL (top-down). In your case, you need to start from the Store Procedures.
2) deploy your service endpoint. As the result of the deployment step, you will have a WSDL available on your application server, that advertise the service interface.
3) generate the static client proxy from the WSDL (service contract).
4) invoke the service using the proxy from step 3 or use dynamic invocation APIs to make direct call, without to use a static proxy.
Bypassing step 3) usually requires a dipper understanding of SOAP linguana, so it's not the easiest way to get started.
Based on the statement you made, it looks like you are starting from step 3)
From the error message, it seams that you are trying to invoke a Web service that was deployed using 'literal' encoding (either document/literal or RPC/literal) with a client generated for RPC-encoded message format. In the JDeveloper Wizard, you have an option to change the message format to RPC/Encoded.
Hope this helps,
eric

DII unexpected encoding style with SharePoint Web Service

I am trying to call a dynamic sharepoint web service in Java using DII (Dynamic Invocation Interface)
but I kept getting error:unexpected encoding style: after the invoke expected=http://schemas.xmlsoap.org/soap/encoding/, actual=
I am trying to call web service - GetWebCollection()
String endPoint="http://%SPSERVER/_vti_bin/Webs.asmx";
String nameSpaceUri = "xmlns:xsi";
String serviceName = "Webs";
String porttype="WebsSoap";
String NS_XSD = "http://www.w3.org/2001/XMLSchema";
ServiceFactory factory =
ServiceFactory.newInstance();
Service service =factory.createService(new QName(serviceName));
QName qport = new QName(porttype);
hpsharepoint.Webs webs = new hpsharepoint.Webs_Impl();
Call call = (Call) webs.createCall(qport);
call.setProperty(call.USERNAME_PROPERTY,kuser);
call.setProperty(call.PASSWORD_PROPERTY,password);
call.setProperty(Call.ENCODINGSTYLE_URI_PROPERTY, "http://schemas.xmlsoap.org/soap/encoding/");
call.setProperty(Call.SOAPACTION_USE_PROPERTY,
new Boolean(true));
call.setProperty(Call.SOAPACTION_URI_PROPERTY,"http://schemas.microsoft.com/sharepoint/soap/GetWebCollection");
call.setTargetEndpointAddress(endPoint);
call.setOperationName(
new QName(nameSpaceUri,"GetWebCollection"));
String[] params = {};
NodeList list=(NodeList)call.invoke(params);
==========================
This is the soap 1.1
==========================
POST /_vti_bin/Webs.asmx HTTP/1.1 Host: <server> Content-Type: text/xml; charset=utf-8 Content-Length: length SOAPAction: "http://schemas.microsoft.com/sharepoint/soap/GetWebCollection" <?xml version="1.0" encoding="utf-8"?> <soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <GetWebCollection xmlns="http://schemas.microsoft.com/sharepoint/soap/" /> </soap:Body> </soap:Envelope>

Jose,
When you work with Web Services, the common development flow is as follow:
1) develop your service endpoint. You can start from JAVA code or PL/SQL package (bottom-up) or from a WSDL (top-down). In your case, you need to start from the Store Procedures.
2) deploy your service endpoint. As the result of the deployment step, you will have a WSDL available on your application server, that advertise the service interface.
3) generate the static client proxy from the WSDL (service contract).
4) invoke the service using the proxy from step 3 or use dynamic invocation APIs to make direct call, without to use a static proxy.
Bypassing step 3) usually requires a dipper understanding of SOAP linguana, so it's not the easiest way to get started.
Based on the statement you made, it looks like you are starting from step 3)
From the error message, it seams that you are trying to invoke a Web service that was deployed using 'literal' encoding (either document/literal or RPC/literal) with a client generated for RPC-encoded message format. In the JDeveloper Wizard, you have an option to change the message format to RPC/Encoded.
Hope this helps,
eric

SOAP adapter and WS with rpc/encoded

Hi All,
Does anyone know if and how the SAP XI 3.0 SOAP Adapter supports WebServices which expects XML messages in rpc/encoded.
Cheers,
FRank

Hi Frank,
I have the same issue and I got a reply from OSS:
This problem is caused by the diversification of the WSDL binding
styles.
A Web service is described by a WSDL document. A WSDL binding
describes how the service is bound to a messaging protocol, particularly
the SOAP messaging protocol. A WSDL SOAP binding can be either an RPC
style binding or a document style binding. A SOAP binding can also have
an encoded use or a literal use. This gives us four style/use models:
- RPC/encoded
- RPC/literal
- document/encoded(It will probably disappear from future versions of
WSDL.)
- document/literal
RPC styled web services have serious interoperability problems. This
is the reason that the rpc style is not in the basic profile
specification of the web interoperability and also it has been
deprecated in the current soap specification. For these reason, the
integration directory does not currently support the RPC style! I would
suggest you to use other document style web service provider if possible
. It's the best way to solve this problem. But if you persist in using
this RPC web service provider, we still have a workaround solution:
you need to convert your RPC wsdl to a document styled wsdl and import
it to the directory and if necessary, you need to add some mapping to
solve some RPC interoperability problems.
In your case,
1. The WSDL file you used is RPC style.
2. The XI SOAP adapter doesn't support the RPC style. It only sends the
document/literal SOAP message which can't be understand by your web
service provider.
One of the significant differences between the SOAP message of RPC
style and that of the document style: the operation name is contained in
the RPC style SOAP message but not in the document's.
However, you can't solve this problem by simply specify a method
name. What you should do is convert your RPC wsdl to a document styled
wsdl. RPC turns out to be a subset of document/literal. This
means for any given RPC WSDL, you can create a completely
equivalent document/literal WSDL that would describe the same wire
messages. Here are the steps for doing this (mostly schema element
declarations).
Solution:
For each RPC operation:
1. For each part in the input and output messages of that operation,
declare a type with the contents described in step 2.
2. Declare an element with the name of the part, the type referenced by
type=". The element form must be unqualified.
3. Declare a global element with the operation name and the namespace
from soap:body/@namespace in the binding. Make the type of this element
the one defined in step 1 for the input message.
4. Declare a global element with the operation name and the word
Response appended to it and the namespace from soap:body/@namespace in
the binding. Make the type of this element the one defined in step 1 for
the output message.
5. Change the input message to contain one part and reference the
element you declared in step 3.
6. Change the output message to contain one part and reference the
element you declared in step 4.
7. Change the style to document in the binding.
After that, import the new WSDL file to the integration directory. You
will find the "method name" appears in the document style SOAP message.
But actually it's the name of the input element which is the same as
the name of the operation. It's just a little trick.
Cheers Stefan

No Serializer found to serialize a 'org.w3c.dom.Element' using encoding style ...

I use oc4j903 and win2k. I write a document style web service following Demo for Stateless Java Document Web Services.
I Create an EAR file using WebServicesAssembler and deploy it .and my config.xml:
<web-service>
<display-name>Stateful Java Document milkdemo Web Service</display-name>
<description>Stateful Java Document milkdemo Web Service Example</description>

<destination-path>./milkdemo.ear</destination-path>

<temporary-directory>./temp</temporary-directory>

<context>/milkdemo</context>

<stateful-java-service>
<interface-name>com.brightdairy.client.sync.SyncServerDoc</interface-name>
<class-name>com.brightdairy.client.sync.SyncServerDocImpl</class-name>

<uri>/milkdemo</uri>

<java-resource>./classes</java-resource>

<message-style>doc</message-style>
</stateful-java-service>

<wsdl-gen>
     <wsdl-dir>wsdl</wsdl-dir>

     <option name="force">true</option>
     <option name="httpServerURL">http://localhost:8888</option>
</wsdl-gen>

<proxy-gen>
     <proxy-dir>proxy</proxy-dir>
     <option name="include-source">true</option>
</proxy-gen>
</web-service>
my webservice java file:
* Title: BrightDairy SOAP demo
* Description:
* Copyright: Copyright (c) 2002
* Company: ufoasia
* @author
* @version 1.0
package com.brightdairy.client.sync;
import java.sql.*;
import java.util.Vector;
import java.util.Iterator;
import org.w3c.dom.Element;
import org.w3c.dom.Document;
import org.w3c.dom.NodeList;
import oracle.xml.parser.v2.XMLDocument;
import oracle.xml.parser.v2.XMLElement;
//import com.brightdairy.client.object.Product;
import com.brightdairy.client.sync.SyncServerDoc;
public class SyncServerDocImpl implements SyncServerDoc {
public SyncServerDocImpl() {
public Element getProductIDList() {
Connection connServer = null;
PreparedStatement stmtServerProduct = null;
ResultSet rsServerProduct = null;
Document doc = new XMLDocument();
Element elProduct = doc.createElement("product");
doc.appendChild(elProduct);
long m_msec;
m_msec = System.currentTimeMillis();
try {
connServer = makeConnection();
System.out.println("1");
stmtServerProduct = connServer.prepareStatement(
"SELECT ID FROM " + SERVER_TABLE_PRODUCT );
System.out.println("");
rsServerProduct = stmtServerProduct.executeQuery();
System.out.println("2");
while(rsServerProduct.next()) {
Element elID = doc.createElement("id");
elID.appendChild(doc.createTextNode(rsServerProduct.getString("ID")));
elProduct.appendChild(elID);
System.out.println("3");;
System.out.println("4");
return doc.getDocumentElement();
} catch(SQLException e) {
e.printStackTrace();
System.out.println("SQL exception has occured");
System.out.println(e.getMessage());
return doc.getDocumentElement();
}finally {
try {
rsServerProduct.close();
stmtServerProduct.close();
connServer.close();
m_msec = System.currentTimeMillis() - m_msec;
System.out.println("6");
System.out.println("getProductIDList:It take time:" m_msec/1000 "s");
} catch(Exception e1) {}
Now my firts question: when i generate the proxy WebServicesAssembler will failure (couldn't import jar.....) and i had imported all jar files,But if i commented proxy-gen , no error.
and my second question: I commented proxy-gen and deployed ite and success. when i invoked it through web page , then error:
java.lang.IllegalArgumentException: No Serializer found to serialize a 'org.w3c.
dom.Element' using encoding style 'http://schemas.xmlsoap.org/soap/encoding/'.
at org.apache.soap.util.xml.XMLJavaMappingRegistry.querySerializer(XMLJa
vaMappingRegistry.java:157)
at org.apache.soap.encoding.soapenc.ParameterSerializer.marshall(Paramet
erSerializer.java:106)
at org.apache.soap.rpc.RPCMessage.marshall(RPCMessage.java:265)
at org.apache.soap.Body.marshall(Body.java:148)
at org.apache.soap.Envelope.marshall(Envelope.java:203)
at org.apache.soap.Envelope.marshall(Envelope.java:161)
at oracle.j2ee.ws.InvocationWrapper.invoke(InvocationWrapper.java:309)
at oracle.j2ee.ws.RpcWebService.doGetRequest(RpcWebService.java:540)
at oracle.j2ee.ws.BaseWebService.doGet(BaseWebService.java:1106)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletReque
stDispatcher.java:721)
at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(Ser
vletRequestDispatcher.java:306)
at com.evermind.server.http.HttpRequestHandler.processRequest(HttpReques
tHandler.java:767)
at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.ja
va:259)
at com.evermind.server.http.HttpRequestHandler.run(HttpRequestHandler.ja
va:106)
at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExec
utor.java:803)
at java.lang.Thread.run(Thread.java:484)
I took much time and couln't get answer ,please help me!!!!!!!!!!!!

Yeah!
I have resolved it .
It take me one day time!
my error is 1: Element which I used is no namespace.
2: no import enough jar files
just so so .
sorry! I am poor in English

Can SAP handle RPC/encoded WSDLs

I am not sure whether this is the right forum for this question, but i'll give it a try:
I have a WSDL file (web service decription) from a 3rd party tool, which is RPC/encoded, and I tried to generated an ABAP proxy class (SAP Basis 7.01). During the generation I get a couple of different errors, and the one that bothers me most is
"incorrect value for attribute use: "encoded"".
When I replace all occurrences of "use="encoded"" with "use="literal"", then the proxy generation will work, but in this case, the web service call will not work anymore (probably because the encoded response from the webservice cannot be read by the proxy class).
What can I do?
Any hints are welcome.

Hi,
It seems only RPC with literal will be supported in future.
Quote from wiki Please see this:
"Some of these combinations are rarely used in practice, such as document/encoded. In general, the literal use is gaining importance, and as far as RPC/encoded is concerned, the Web Services Interoperability Organization (WS-I) in its Basic Profile Version 1.0a of August 2003 ruled out the use of SOAP encoding with web services. Document/literal and RPC/literal will be the only allowed style/use combinations in the future."
Detail wiki is available here: http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/c018da90-0201-0010-ed85-d714ff7b7019
Regards,
Gourav
Edited by: Gourav Khare on Oct 13, 2009 12:28 AM

Dose javax.xml.rpc.encoding.XMLType has anything to represent void type

Hi All,
Is it possible to use XML types to represent a void(type).
In other words, dose "javax.xml.rpc.encoding.XMLType" has anything to represent void type.
Here is my code snippet...
At the Service Endpoint i have a service
public void invokeBatchProcess(String actType)
    throws   java.rmi.RemoteException; At the Web-Service Client side i'm invoking this webservice using DII.
Not sure how to set the return type to Call object.
Client Code:
ServiceFactory serviceFactory = ServiceFactory.newInstance();
//Service Name
Service service = serviceFactory.createService(new QName(
          IConstants.DEFAULT_SERVICE_NAME));
//Port Name
QName port = new QName(IConstants.DEFAULT_SERVICE_PORT);
Call serviceCall = service.createCall(port);
serviceCall.setProperty(IConstants.URI_ENCODING_PROPERTY,IConstants.URI_ENCODING);
serviceCall.setProperty(Call.SOAPACTION_USE_PROPERTY,new Boolean(true));
//Target EndPoint
serviceCall.setTargetEndpointAddress(IConstants.DEFAULT_URL);
//OperationName
serviceCall.setOperationName(new QName(IConstants.DEFAULT_SERVICE_OPERATION_NAME));
serviceCall.addParameter(
"arg1",new QName("http://schemas.xmlsoap.org/soap/encoding/","string"),
ParameterMode.IN);
//How to use XMLType to represent void ???
serviceCall.setReturnType(????????) Greatly appreciate your help.
Priya.Jlus
IIMS-NewZealand.

Hello-
Sorry for the delay in responding.
Given the following dii client you will not that the return parameter does not need to be set on the call object-
The call is invoked in the normal way using the invoke method-
the invokeOneWay method performs calls asynchonously and no soap message is returned to the client-
The client below that has a void return parameter does
deserialize a soap response message, but the message contains no data.
public static void main(String[] args) {
try {
ServiceFactory factory =
ServiceFactory.newInstance();
Service service =
factory.createService(new QName(BODY_NAMESPACE_VALUE,qnameService));
QName port = new QName(BODY_NAMESPACE_VALUE, qnamePort);
Call call = service.createCall(port);
call.setTargetEndpointAddress(endpoint);
          call.setProperty(Call.SOAPACTION_USE_PROPERTY,
new Boolean(true));
call.setProperty(Call.SOAPACTION_URI_PROPERTY, "");
call.setProperty(ENCODING_STYLE_PROPERTY, URI_ENCODING);
               call.setProperty(Call.OPERATION_STYLE_PROPERTY, "rpc");
                    HelloClient client = new HelloClient();
                    client.sayHelloNoReturn(call);
} catch (Exception ex) {
ex.printStackTrace();
     void sayHelloNoReturn(Call call1) {
try {
          call1.setOperationName(new QName(BODY_NAMESPACE_VALUE, "sayHelloVoid"));
          boolean b = call1.isParameterAndReturnSpecRequired(
     new QName(BODY_NAMESPACE_VALUE, "sayHelloVoid"));
               if(true) {
                    //call1.setReturnType(new QName(NS_XSD, "string"),
                    //          java.lang.String.class);
                    call1.removeAllParameters();
                    call1.addParameter("String_1", new QName(NS_XSD,
                         "string"), java.lang.String.class, ParameterMode.IN);
                    Object[] params = { "foowho" };
                    call1.invoke(params);
} catch (Exception e) {
     System.out.println("Caught exception: " + e.getMessage());
e.printStackTrace();
The following is the message that passes from the dii client to the service, and the service response-
Request
Content-Type: text/xml; charset="utf-8"
Content-Length: 482
SOAPAction: ""
<?xml version="1.0" encoding="UTF-8"?>
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:enc="http://schemas.xmlsoap.org/soap/encoding/" env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><env:Body><ans1:sayHelloVoid xmlns:ans1="http://hello.org/wsdl"><String_1 xsi:type="xsd:string">foowho</String_1></ans1:sayHelloVoid></env:Body></env:Envelope>
Response
Http Status Code: 200
Content-Type: text/xml; charset="utf-8"
Content-Length: 482
SOAPAction: ""
<?xml version="1.0" encoding="UTF-8"?>
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:enc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns0="http://hello.org/types" env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><env:Body><ans1:sayHelloVoidResponse xmlns:ans1="http://hello.org/wsdl"/></env:Body></env:Envelope>******************
The wsdl is as follows:
<?xml version="1.0" encoding="UTF-8"?>
<definitions name="HelloService" targetNamespace="http://hello.org/wsdl" xmlns:tns="http://hello.org/wsdl" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/">
<types/>
<message name="HelloIF_sayHello">
<part name="String_1" type="xsd:string"/></message>
<message name="HelloIF_sayHelloResponse">
<part name="result" type="xsd:string"/></message>
<message name="HelloIF_sayHelloVoid">
<part name="String_1" type="xsd:string"/></message>
<message name="HelloIF_sayHelloVoidResponse"/>
<message name="HelloIF_sayHelloVoid2">
<part name="String_1" type="xsd:string"/>
<part name="int_2" type="xsd:int"/></message>
<message name="HelloIF_sayHelloVoid2Response"/>
<portType name="HelloIF">
<operation name="sayHello" parameterOrder="String_1">
<input message="tns:HelloIF_sayHello"/>
<output message="tns:HelloIF_sayHelloResponse"/></operation>
<operation name="sayHelloVoid" parameterOrder="String_1">
<input message="tns:HelloIF_sayHelloVoid"/>
<output message="tns:HelloIF_sayHelloVoidResponse"/></operation>
<operation name="sayHelloVoid2" parameterOrder="String_1 int_2">
<input message="tns:HelloIF_sayHelloVoid2"/>
<output message="tns:HelloIF_sayHelloVoid2Response"/></operation></portType>
<binding name="HelloIFBinding" type="tns:HelloIF">
<operation name="sayHello">
<input>
<soap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded" namespace="http://hello.org/wsdl"/></input>
<output>
<soap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded" namespace="http://hello.org/wsdl"/></output>
<soap:operation soapAction=""/></operation>
<operation name="sayHelloVoid">
<input>
<soap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded" namespace="http://hello.org/wsdl"/></input>
<output>
<soap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded" namespace="http://hello.org/wsdl"/></output>
<soap:operation soapAction=""/></operation>
<operation name="sayHelloVoid2">
<input>
<soap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded" namespace="http://hello.org/wsdl"/></input>
<output>
<soap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" use="encoded" namespace="http://hello.org/wsdl"/></output>
<soap:operation soapAction=""/></operation>
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="rpc"/></binding>
<service name="HelloService">
<port name="HelloIFPort" binding="tns:HelloIFBinding">
<soap:address location="REPLACE_WITH_ACTUAL_URL"/></port></service></definitions>
I hope this has been helpful and thank you for
using jaxrpc

RPC/encoded style

Similar Messages

Maybe you are looking for