OSB not adding SOAP-ENV:encodingStyle attribute, invoke fails

Hi, I have a WSDL that when inspected by XMLSpy, creates the following payload.
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
 <SOAP-ENV:Body>
 <m:logOut xmlns:m="http://konnex.aarp.org/wsdl/HartfordServicesSecure" SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
 <String_1 xsi:type="xsd:string">String</String_1>
 </m:logOut>
 </SOAP-ENV:Body>
</SOAP-ENV:Envelope>
When I try to invoke this via OSB, I get the following message.
<env:Envelope env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/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://konnex.aarp.org/types/HartfordServicesSecure">
 <env:Body>
 <env:Fault>
 <faultcode>env:Client</faultcode>
 <faultstring>JAXRPCTIE01: caught exception while handling request: unexpected encoding style: expected=http://schemas.xmlsoap.org/soap/encoding/, actual=</faultstring>
 </env:Fault>
 </env:Body>
</env:Envelope>
The reason is because OSB is not putting in the *SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/* attribute. I verified this in obtunnel.
I'm currently trying to work around this in OSB using xquery but so far I've had no luck.
Thanks in Advance.

hi,
I have two policies applies on business service :
1. Password digest policy
<wsp:Policy wsu:Id="PasswrdDigest" xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy" xmlns:wssp="http://www.bea.com/wls90/security/policy" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
<wssp:Identity>
 <wssp:SupportedTokens>
 <wssp:SecurityToken TokenType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#UsernameToken">
 <wssp:UsePassword Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordDigest"/>
 </wssp:SecurityToken>
 </wssp:SupportedTokens>
 </wssp:Identity>
</wsp:Policy>
2. Message Interval Policy
<wsp:Policy wsu:Id="MessageAge" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:wsp="http://schemas.xmlsoap.org/ws/2004/09/policy">
<wssp:MessageAge Age="60" xmlns:wssp="http://www.bea.com/wls90/security/policy"/>
</wsp:Policy>
Please share your views.

Similar Messages

XI SOAP-ENV request!!!

Hi all,
I have a problem that is not resolved yet and Im feeling quite worried because I used up all the hypotheses that knew!!! I did a test that it gave a light, where problem are placed, but I dont know how I can fix it. I hope that somebody could help me
Calling the web service directly via an external tool as a web service client using soap sender adapter, the request SOAP-ENV is:
<?xml version="1.0" encoding="UTF-8" ?><SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xs="http://www.w3.org/2001/XMLSchema"><SOAP-ENV:Body SOAP-ENV:encodingStyle='http://schemas.xmlsoap.org/soap/encoding/'><ns1:send xmlns:ns1='prt:service:pt.edp.sync'><send_1_param2 xsi:type='xs:string'>teste</send_1_param2></ns1:send></SOAP-ENV:Body></SOAP-ENV:Envelope>
And it works fine!
Using the same external tool also as a web service client, but now trough XI, the SOAP-ENV request is a little bit different: (the tag with send method it lack!!!)

<ns1:send_1_param2 xmlns:ns1='prt:service:pt.edp.sync'>teste</ns1:send_1_param2>

It seams that method send is not being invoked, if you look to the previous SOAP-ENV you see the tag with method <ns1:send > before tag with input parameter <ns1:send_1_param2> I think that this tag should come into soap request invoked by XI. For one reason that I dont know, this tag doesnt come... and when I look to the log of web service provider invoked from XI (is a SAP EP) the log gives me this message:
Method with name send_1_param2 is not defined in wsdl file
[EXCEPTION]
java.lang.NoSuchMethodException
It seams that XI wants to invoke a method with a wrong name send_1_param2; the method to be invoked should be send and not send_1_param2!!! Can anybody explain me why this happening? Did I forget something, some configuration steps?
Any help are appreciated.
Regards,
Ricardo.

Hi guys,
Here the answer like I promise!
All I get is a little explanation about web services rpc-styled in SOAP FAQ (note 856597) under question: Q: Can I convert an RPC styled WSDL to a document styled WSDL?
Some RPC styled service implementations have problems with such non conformant SOAP service. Therefore, we also need to adjust the message accordingly.
First we need to find what kind of elements (tags) are missing on the soap request/response and add these elements (adjust the message accordingly).
I fixed my problem using XSLT extension (ABAP Engine). All I did was following the steps provided in the Robert Eijpe weblog /people/r.eijpe/blog/2005/11/04/using-abap-xslt-extensions-for-xi-mapping
But you also could create your own request using graphical mapping and add the missing tags. In my case a just only needed to add <operator> tag to invoke the right method.
I test with both (XSLT and Graphical mapping) and it works
I hope it helps anybody with identical problems.
Cheers,
Ricardo.

SOAP:ENV Error: Resource..not found on this server

I created a simple java class with a method that returns org.w3c.dom.Element type.
Created web service for this class and method in Jdeveloper.
Deployed this web service in OC4J locally (as explained by other web services examples).
Then I created a Client Stub for this web service (.wsdl file).
When testing this client stub ( I followed the same steps as mentioned in OTN DEPT/EMP Web Service), I get the following exception:
D:\JDEVELOPER\jdk\bin\javaw.exe -ojvm -classpath D:\JDEVELOPER\jdev\mywork\MyWorkspace\MyProject2\classes;D:\JDEVELOPER\jdev\lib\jdev-rt.jar;D:\JDEVELOPER\jdbc\lib\classes12.jar;D:\JDEVELOPER\jdbc\lib\nls_charset12.jar;D:\JDEVELOPER\jdev\lib\jdev-rt.jar;D:\JDEVELOPER\soap\lib\soap.jar;D:\JDEVELOPER\lib\xmlparserv2.jar;D:\JDEVELOPER\jlib\javax-ssl-1_2.jar;D:\JDEVELOPER\jlib\jssl-1_2.jar;D:\JDEVELOPER\j2ee\home\lib\activation.jar;D:\JDEVELOPER\j2ee\home\lib\mail.jar;D:\JDEVELOPER\j2ee\home\lib\http_client.jar;D:\JDEVELOPER\lib\xmlparserv2.jar;D:\JDEVELOPER\lib\xmlcomp.jar;D:\JDEVELOPER\rdbms\jlib\xsu12.jar GetProductsClient
[SOAPException: faultCode=SOAP-ENV:Protocol; msg=Unsupported response content type "text/html", must be: "text/xml". Response was:
<HTML><HEAD><TITLE>404 Not Found</TITLE></HEAD><BODY><H1>404 Not Found</H1>Resource /MyWorkspace-MyProject2-context-root/GetProducts not found on this server</BODY></HTML>
The SOAP response is as bellow:
HTTP/1.1 404 Not Found
Date: Wed, 27 Nov 2002 15:36:27 GMT
Server: Oracle9iAS (9.0.3.0.0) Containers for J2EE
Content-Length: 171
Connection: Close
Content-Type: text/html
<HTML><HEAD><TITLE>404 Not Found</TITLE></HEAD><BODY><H1>404 Not Found</H1>Resource /MyWorkspace-MyProject2-context-root/GetProducts not found on this server</BODY></HTML>
The Debug shows, the Method getProductsXM() in the client stub is failing at
Response response = call.invoke(endpointURL, "");
This appears to be generating fault and the code is throughing exception which is not casted in to a Element type.
Not sure what is causing this to fail. And I have not toucjed/ changed the URI for this webservice myself at all. Whatever URIs or Name spaces are there, they are all generarted by JDeveloper.
I was trying to create a web service that display/return Resultset.
Any feedback/suggestions ? I would appreciate if you can point me to some sample code that does this ( returning Resultset as XML -<ROWSET> Element)
Thanks,
Madhu

Does this do the trick?
Server side class:
import org.w3c.dom.*;
import oracle.xml.parser.v2.*;
public class Employee
public Employee ()
public Element getEmployeeElement(){
Document doc = new XMLDocument();
Element elAdd = doc.createElement( "employee");
Element elA = doc.createElement( "name");
elA.appendChild(doc.createTextNode("Mike"));
elAdd.appendChild(elA);
doc.appendChild(elAdd);
return doc.getDocumentElement();
Generated Interface from JDev:
* Generated by the Oracle9i JDeveloper Web Services Interface Generator
* Date Created: Wed Nov 27 11:42:37 PST 2002
* This interface lists the subset of public methods that you
* selected for inclusion in your web service's public interface.
* It is referenced in the web.xml deployment descriptor for this service.
* This file should not be edited.
public interface IEmployee
public org.w3c.dom.Element getEmployeeElement();
Generated client with a print method to output the result (using WSDL generated by JDeveloper):
import oracle.soap.transport.http.OracleSOAPHTTPConnection;
import org.apache.soap.encoding.soapenc.BeanSerializer;
import org.apache.soap.encoding.SOAPMappingRegistry;
import org.apache.soap.util.xml.QName;
import java.net.URL;
import org.apache.soap.Constants;
import org.apache.soap.Fault;
import org.apache.soap.SOAPException;
import org.apache.soap.rpc.Call;
import org.apache.soap.rpc.Parameter;
import org.apache.soap.rpc.Response;
import org.w3c.dom.Element;
import java.util.Vector;
import java.util.Properties;
import oracle.xml.parser.v2.*;
* Generated by the Oracle9i JDeveloper Web Services Stub/Skeleton Generator.
* Date Created: Wed Nov 27 11:39:29 PST 2002
* WSDL URL: file:/D:/demo/Workspace5/Project1/src/Employee.wsdl
public class EmployeeStub
public EmployeeStub()
m_httpConnection = new OracleSOAPHTTPConnection();
m_smr = new SOAPMappingRegistry();
public static void main(String[] args)
try
EmployeeStub stub = new EmployeeStub();
// Add your own code here.
Element e = stub.getEmployeeElement();
((XMLElement)e).print(System.out);
catch(Exception ex)
ex.printStackTrace();
public String endpoint = "http://127.0.0.1:8888/Workspace5-Project1-context-root/Employee";
private OracleSOAPHTTPConnection m_httpConnection = null;
private SOAPMappingRegistry m_smr = null;
public Element getEmployeeElement() throws Exception
Element returnVal = null;
URL endpointURL = new URL(endpoint);
Call call = new Call();
call.setSOAPTransport(m_httpConnection);
call.setTargetObjectURI("Employee");
call.setMethodName("getEmployeeElement");
call.setEncodingStyleURI(Constants.NS_URI_LITERAL_XML);
Vector params = new Vector();
call.setParams(params);
call.setSOAPMappingRegistry(m_smr);
Response response = call.invoke(endpointURL, "");
if (!response.generatedFault())
Parameter result = response.getReturnValue();
returnVal = (Element)result.getValue();
else
Fault fault = response.getFault();
throw new SOAPException(fault.getFaultCode(), fault.getFaultString());
return returnVal;
public void setMaintainSession(boolean maintainSession)
m_httpConnection.setMaintainSession(maintainSession);
public boolean getMaintainSession()
return m_httpConnection.getMaintainSession();
public void setTransportProperties(Properties props)
m_httpConnection.setProperties(props);
public Properties getTransportProperties()
return m_httpConnection.getProperties();
Mike.

Error with Do Not use SOAP envelope

All,
I used the do not send SOAP envelope option in the SOAP receiver adapter.
Instead of XSLT, I used JAVA mapping to create the entire SOAP message ( Am more comfortable with Java and this is just a trial) , and this is the output of my java mapping with the SOAP envelope created,
<?xml version="1.0" encoding="UTF-8"?><soap:Envelope xmlns:soap="http://www.w3.org/2001/12/soap-envelope"soap:encodingStyle="http://www.w3.org/2001/12/soap-encoding"><soap:Header></soap:Header><soap:Body><ns1:GetQuote xmlns:ns1="http://www.webserviceX.NET/"><ns1:symbol>SAP</ns1:symbol></ns1:GetQuote></soap:Body></soap:Envelope>
Am using the STOCK Quote for testing purposes and this is the error I am getting when testing my interface,
<faultstring>System.Web.Services.Protocols.SoapException: Server found request content type to be '', but expected 'text/xml'. at System.Web.Services.Protocols.SoapServerProtocol.ReadParameters() at System.Web.Services.Protocols.WebServiceHandler.Invoke() at System.Web.Services.Protocols.WebServiceHandler.CoreProcessRequest()</faultstring>
Any directions / inputs on how to resolve this issue?
Regards,
Bhavesh

Henrique,
Tried various permutations~~ The only new error / progress seems to be for this,
SOAPAction "http://www.webserviceX.NET/GetQuote"
This is giving me an error ,
HTTP server code 400 reason Bad Request explanation <h1>Bad Request (Invalid Header Name)</h1>
Also, tried by adding the Colon after SOAPAction,
SOAPAction: "http://www.webserviceX.NET/GetQuote"
Same error
Final thing i guess is to make SOAPAction all small as soapaction and check if it works. Will let you know.
Regards,
Bhavesh

SOAP Envelope encodingStyle

Hi experts,
I have a PI SOAP Receiver, sending to a Java Powerbuilder app. I am getting an HTTP 200, but with an error message in SXMB_MONI:
<SAP:Category>XIAdapterFramework</SAP:Category>
<SAP:Code area="MESSAGE">GENERAL</SAP:Code>
<SAP:AdditionalText>com.sap.aii.af.ra.ms.api.DeliveryException: java.lang.NullPointerException; HTTP 200 OK</SAP:AdditionalText>
When I execute the same scenario using soapUI instead of PI, using the same SOAP Payload, I get no SOAP body, only this HTTP Response (HTTP 200 OK as well):
" No mapping found for 'class java.lang.String' using encoding style 'http://xml.apache.org/xml-soap/literalxml' "
When I change the Payload slightly in soapUI, ie. adding an encodingStyle attribute to the SOAP Envelope, I get the expected response message ("Test OK").
To summarize:
PI sends this SOAP Envelope, which the remote app cannot accept (no mapping found):
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
When the SOAP Envelope is modified like below, the test is ok:
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"
SOAP:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
Any ideas how I can add an encodingStyle attribute ?
kr,
Peter Glas

An sdn search gave me this thread to create custom SOAP envelop
Generating SOAP Envelope when DO NOT USE ENVELOPE option is marked

SOAP-ENV:IOException; msg=SSL handshake failed: SSLProtocolErr

Getting following error while invoking webservice over ssl.
"SOAP-ENV:IOException; msg=SSL handshake failed: SSLProtocolErr"
We generated webservice java stub using JDeveloper based on wsdl provided to us from 3rd party. We are able to test this webservice successfully without ssl . Once ssl is enabled by the 3rd party webservice provider we faced
"java.lang.UnsatisfiedLinkError: no njssl9 in java.library.path" error in JDeveloper.
In JDeveloper we were able to resolve this by following details provided at
Lehmann's web log on "Securing a Web Service - Client SSL" (http://radio.weblogs.com/0132036/2004/02/13.html ).
We then run the same java stub from oracle application server 9iAS 1.0.2.2.2. This is when we get error
"SOAP-ENV:IOException; msg=SSL handshake failed: SSLProtocolErr"
Debugging further we see that in 9iAS we have following in our class path.
..iAS/jlib/jssl-1_1.jar:..iAS/jlib/javax-ssl-1_1.jar:..iAS/soap/webapps/soap/WEB-INF/lib/soap.jar
we took the same files and added to libraries in JDeveloper and are able to reproduce the same error in JDeveloper. We turned on Debug on oracle.jssl.debug and with that we see following details
instantiate the hashtable
SocketTable write Enter fdin 1
SocketTable write offset 0 length 72
SocketTable write: 72 bytes
SocketTable read Enter
SocketTable read: 1 bytes
SocketTable read Enter
SocketTable read: 2 bytes
SSLSocketImpl close Thread:main
In close removing fd 1Thread main
[SOAPException: faultCode=SOAP-ENV:IOException; msg=SSL handshake failed: SSLProtocolErr...
Any suggestions on how to resolve this error in oracle application server 9iAS ?
Note: We run Oracle E-Business Suite on this same 9iAS so any change we make should not impact the oracle applications running on this server.

hi,
thi sis very simple soloution for this. open the wsdl into the internet explorer. when wsdl file open save this wsdl with the .xml extension. when u want to make dat contorl or web sekelton or proxy dont use the hhtps:// ????????/ url give the path there for the .xml file which u save for this. i am sure u will invoke all the services which is provoider by the web service.
have nice day
best regards

BPEL process times out when SOAP-ENV:Fault is received from service.

Hi - I have a BPEL process identical to one in 10.1.2.0.2. If I execute the same test, the BPEL console displays the following on the console for version 10.1.2.0.2.
<Response>Clientwhen invoking endpointAddress 'http://galileo.wlgore.com:5555/soap/default', [ISS.0088.9134] Exception occurred while processing the body of the messageAxisFault faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Client faultSubcode: faultString: [ISS.0088.9134] Exception occurred while processing the body of the message faultActor: http://galileo.wlgore.com:5555/soap/default faultNode: faultDetail: {http://www.webMethods.com/2001/10/soap/encoding}exception: <className>com.wm.pkg.art.error.DetailedServiceException</className>
 <message lang="">[ART.117.4002] Adapter Runtime (Adapter Service): Unable to invoke adapter service GORE_DSI_Services.AdaptorService:WorkOrderCompletion. BSFN error code: 2 Number of error: 1 Error item 1 ErrorLevel : 1 ErrorID : 0 DDItem : 0115 lineNumber : 5371 fileName : nd3n1114.c subText : alphaDescription : Error: Work Order Number Invalid glossaryText : CAUSE . . . . The Work Order Number entered does not exist in the Work Order Master file (F4801). RESOLUTION. . Either enter the correct Work Order Number or create a new Work Order for the number on the display. javax.resource.ResourceException: BSFN error code: 2 Number of error: 1 Error item 1 ErrorLevel : 1 ErrorID : 0 DDItem : 0115 lineNumber : 5371 fileName : nd3n1114.c subText : alphaDescription : Error: Work Order Number Invalid glossaryText : CAUSE . . . . The Work Order Number entered does not exist in the Work Order Master file (F4801). RESOLUTION. . Either enter the correct Work Order Number or create a new Work Order for the number on the display. at com.psft.xpi.adapter.erp.service.BSFNExecuteTemplateImpl.execute(BSFNExecuteTemplateImpl.java:306) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.psft.xpi.adapter.erp.service.BSFNExecuteTemplate.execute(BSFNExecuteTemplate.java:134) at com.wm.adk.cci.interaction.WmInteraction.execute(WmInteraction.java:70) at com.wm.pkg.art.ns.AdapterServiceNode.invokeService(AdapterServiceNode.java:596) at com.wm.pkg.art.ns.ARTNSService.baseInvoke(ARTNSService.java:47) at com.wm.app.b2b.server.invoke.InvokeManager.process(InvokeManager.java:554) at com.wm.app.b2b.server.invoke.StatisticsProcessor.process(StatisticsProcessor.java:44) at com.wm.app.b2b.server.invoke.ServiceCompletionImpl.process(ServiceCompletionImpl.java:221) at com.wm.app.b2b.server.invoke.ValidateProcessor.process(ValidateProcessor.java:49) at com.wm.app.b2b.server.ACLManager.process(ACLManager.java:194) at com.wm.app.b2b.server.invoke.DispatchProcessor.process(DispatchProcessor.java:39) at com.wm.app.b2b.server.AuditLogManager.process(AuditLogManager.java:384) at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:486) at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:359) at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:246) at com.wm.app.b2b.server.BaseService.invoke(BaseService.java:155) at com.wm.lang.flow.FlowInvoke.invoke(FlowInvoke.java:324) at com.wm.lang.flow.FlowState.invokeNode(FlowState.java:580) at com.wm.lang.flow.FlowState.step(FlowState.java:438) at com.wm.lang.flow.FlowState.invoke(FlowState.java:403) at com.wm.app.b2b.server.FlowSvcImpl.baseInvoke(FlowSvcImpl.java:1749) at com.wm.app.b2b.server.invoke.InvokeManager.process(InvokeManager.java:554) at com.wm.app.b2b.server.invoke.StatisticsProcessor.process(StatisticsProcessor.java:44) at com.wm.app.b2b.server.invoke.ServiceCompletionImpl.process(ServiceCompletionImpl.java:221) at com.wm.app.b2b.server.invoke.ValidateProcessor.process(ValidateProcessor.java:49) at com.wm.app.b2b.server.ACLManager.process(ACLManager.java:194) at com.wm.app.b2b.server.invoke.DispatchProcessor.process(DispatchProcessor.java:39) at com.wm.app.b2b.server.AuditLogManager.process(AuditLogManager.java:384) at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:486) at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:359) at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:246) at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:113) at com.wm.app.b2b.server.Service.doInvoke(Service.java:607) at com.wm.app.b2b.server.Service.doInvoke(Service.java:556) at wm.server.soap.envelope(soap.java:98) at sun.reflect.GeneratedMethodAccessor35.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.wm.app.b2b.server.JavaService.baseInvoke(JavaService.java:287) at com.wm.app.b2b.server.invoke.InvokeManager.process(InvokeManager.java:554) at com.wm.app.b2b.server.invoke.StatisticsProcessor.process(StatisticsProcessor.java:44) at com.wm.app.b2b.server.invoke.ServiceCompletionImpl.process(ServiceCompletionImpl.java:221) at com.wm.app.b2b.server.invoke.ValidateProcessor.process(ValidateProcessor.java:49) at com.wm.app.b2b.server.ACLManager.process(ACLManager.java:194) at com.wm.app.b2b.server.invoke.DispatchProcessor.process(DispatchProcessor.java:39) at com.wm.app.b2b.server.AuditLogManager.process(AuditLogManager.java:384) at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:486) at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:359) at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:246) at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:128) at com.wm.app.b2b.server.HTTPSOAPHandler._process(HTTPSOAPHandler.java:457) at com.wm.app.b2b.server.HTTPSOAPHandler.process(HTTPSOAPHandler.java:111) at com.wm.app.b2b.server.Dispatch.run(Dispatch.java:298) at com.wm.util.pool.PooledThread.run(PooledThread.java:105) at java.lang.Thread.run(Thread.java:534) </message>
</Response>
With this version, however, we either receive "java.lang.IllegalStateException: "Cannot call setRollbackOnly() current thread is NOT associated with a transaction" or a timeout error.
I captured the return message from both servers and it is identical (shown below):
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance" xmlns:xsd="http://www.w3.org/1999/XMLSchema">
 <SOAP-ENV:Body>
 <SOAP-ENV:Fault>
 <faultcode>SOAP-ENV:Client</faultcode>
 <faultstring>[ISS.0088.9134] Exception occurred while processing the body of the message</faultstring>
 <faultactor>http://galileo.wlgore.com:5555/soap/default </faultactor>
 <detail xmlns:webM="http://www.webMethods.com/2001/10/soap/encoding">
 <webM:exception>
 <webM:className>com.wm.pkg.art.error.DetailedServiceException</webM:className>
 <webM:message xml:lang="">="">[ART.117.4002] Adapter Runtime (Adapter Service): Unable to invoke adapter service GORE_DSI_Services.AdaptorService:WorkOrderCompletion. BSFN error code: 2 Number of error: 1 Error item 1 ErrorLevel : 1 ErrorID : 0 DDItem : 0115 lineNumber : 5371 fileName : nd3n1114.c subText : alphaDescription : Error: Work Order Number Invalid glossaryText : CAUSE . . . . The Work Order Number entered does not exist in the Work Order Master file (F4801). RESOLUTION. . Either enter the correct Work Order Number or create a new Work Order for the number on the display. javax.resource.ResourceException: BSFN error code: 2 Number of error: 1 Error item 1 ErrorLevel : 1 ErrorID : 0 DDItem : 0115 lineNumber : 5371 fileName : nd3n1114.c subText : alphaDescription : Error: Work Order Number Invalid glossaryText : CAUSE . . . . The Work Order Number entered does not exist in the Work Order Master file (F4801). RESOLUTION. . Either enter the correct Work Order Number or create a new Work Order for the number on the display. at com.psft.xpi.adapter.erp.service.BSFNExecuteTemplateImpl.execute(BSFNExecuteTemplateImpl.java:306) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.psft.xpi.adapter.erp.service.BSFNExecuteTemplate.execute(BSFNExecuteTemplate.java:134) at com.wm.adk.cci.interaction.WmInteraction.execute(WmInteraction.java:70) at com.wm.pkg.art.ns.AdapterServiceNode.invokeService(AdapterServiceNode.java:596) at com.wm.pkg.art.ns.ARTNSService.baseInvoke(ARTNSService.java:47) at com.wm.app.b2b.server.invoke.InvokeManager.process(InvokeManager.java:554) at com.wm.app.b2b.server.invoke.StatisticsProcessor.process(StatisticsProcessor.java:44) at com.wm.app.b2b.server.invoke.ServiceCompletionImpl.process(ServiceCompletionImpl.java:221) at com.wm.app.b2b.server.invoke.ValidateProcessor.process(ValidateProcessor.java:49) at com.wm.app.b2b.server.ACLManager.process(ACLManager.java:194) at com.wm.app.b2b.server.invoke.DispatchProcessor.process(DispatchProcessor.java:39) at com.wm.app.b2b.server.AuditLogManager.process(AuditLogManager.java:384) at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:486) at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:359) at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:246) at com.wm.app.b2b.server.BaseService.invoke(BaseService.java:155) at com.wm.lang.flow.FlowInvoke.invoke(FlowInvoke.java:324) at com.wm.lang.flow.FlowState.invokeNode(FlowState.java:580) at com.wm.lang.flow.FlowState.step(FlowState.java:438) at com.wm.lang.flow.FlowState.invoke(FlowState.java:403) at com.wm.app.b2b.server.FlowSvcImpl.baseInvoke(FlowSvcImpl.java:1749) at com.wm.app.b2b.server.invoke.InvokeManager.process(InvokeManager.java:554) at com.wm.app.b2b.server.invoke.StatisticsProcessor.process(StatisticsProcessor.java:44) at com.wm.app.b2b.server.invoke.ServiceCompletionImpl.process(ServiceCompletionImpl.java:221) at com.wm.app.b2b.server.invoke.ValidateProcessor.process(ValidateProcessor.java:49) at com.wm.app.b2b.server.ACLManager.process(ACLManager.java:194) at com.wm.app.b2b.server.invoke.DispatchProcessor.process(DispatchProcessor.java:39) at com.wm.app.b2b.server.AuditLogManager.process(AuditLogManager.java:384) at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:486) at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:359) at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:246) at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:113) at com.wm.app.b2b.server.Service.doInvoke(Service.java:607) at com.wm.app.b2b.server.Service.doInvoke(Service.java:556) at wm.server.soap.envelope(soap.java:98) at sun.reflect.GeneratedMethodAccessor35.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.wm.app.b2b.server.JavaService.baseInvoke(JavaService.java:287) at com.wm.app.b2b.server.invoke.InvokeManager.process(InvokeManager.java:554) at com.wm.app.b2b.server.invoke.StatisticsProcessor.process(StatisticsProcessor.java:44) at com.wm.app.b2b.server.invoke.ServiceCompletionImpl.process(ServiceCompletionImpl.java:221) at com.wm.app.b2b.server.invoke.ValidateProcessor.process(ValidateProcessor.java:49) at com.wm.app.b2b.server.ACLManager.process(ACLManager.java:194) at com.wm.app.b2b.server.invoke.DispatchProcessor.process(DispatchProcessor.java:39) at com.wm.app.b2b.server.AuditLogManager.process(AuditLogManager.java:384) at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:486) at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:359) at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:246) at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:128) at com.wm.app.b2b.server.HTTPSOAPHandler._process(HTTPSOAPHandler.java:457) at com.wm.app.b2b.server.HTTPSOAPHandler.process(HTTPSOAPHandler.java:111) at com.wm.app.b2b.server.Dispatch.run(Dispatch.java:298) at com.wm.util.pool.PooledThread.run(PooledThread.java:105) at java.lang.Thread.run(Thread.java:534)</webM:message>
 </webM:exception>
 </detail>
 </SOAP-ENV:Fault>
 </SOAP-ENV:Body>
</SOAP-ENV:Envelope>
Thanks,
RM

We have tested this same scenario for several services and are experiencing the same result... timing out instead of returning the fault. This is a critical issue for us and would prevent us from implementing this software.

Java WSDP 1.4 is not parsing SOAP Exceptions

We used Java WSDP 1.4 toolkit to generate stubs for webservices. We used Tomcat 5.1 as the web container. When methods of the webservice are invoked which do not return SOAP exception responses, WSDP is able to properly parse the response and display the resutls correctly. But when the responses contains SOAP exceptions, WSDP always returns
"java.rmi.RemoteException: Runtime exception; nested exception is: trailing block elements must have an id attribute".
But other toolkits like Axis 1.1,.Net,ColdFusionMX,Glue are returning proper exceptions messages. The following is the exception message received from the other toolkits for the same method invocation.
"Exception has been thrown by the target of an invocation. '1000:Invalid data source name 'invalid_String'"
Apart from Java WSDP all the other toolkits that we mentioned are able to parse the exception message properly and display the same.
Any ideas why the toolkit is behaving like this. All the versions of Java WSDP that have come till date have a similar problem. We would be happy to hear any responses for the problem the we are facing in Java WSDP 1.4. At present we have decided not to use the toolkit for any web service development.

Am specifying the URL of the WSDL file for which we are unable to get proper SOAP Exceptions, whenever they are generated. Whenever we give valid values while invoking the methods, the response is properly parsed, but when a SOAP Exception is supposed to be generated, it generally returns the Runtime exception that we mentioned. Can you please look into it and identify the reason about why it is failing. In case you are able to run it through properly, please attach the code that would make it work properly.
The URL is :
http://arcweb.esri.com/services/v2/PlaceFinderSample.wsdl

Did not find needed xsi:type attribute on element anyType

The followings exception is thrown when using the access a web service using the
proxy jar.
The return xml contains
<debts xm:bind="debts is return.safaccount.debts">
<anyType xm:multiple="debt in return.safaccount.debts">{debt}</anyType>
</debts>
debts is a vector contains Serializable Object class.
How do you resolve this?
<Nov 14, 2002 2:36:27 PM ICT> <Error> <HTTP> <101019> <[ServletContext(id=553030
0,name=EAIService,context-path=/EAIService)] Servlet failed with IOException
java.rmi.RemoteException: web service invoke failed; nested exception is:
javax.xml.soap.SOAPException: failed to deserialize xml:weblogic.xml.sch
ema.binding.DeserializationException: did not find needed xsi:type attribute on
element <anyType>
javax.xml.soap.SOAPException: failed to deserialize xml:weblogic.xml.schema.bind
ing.DeserializationException: did not find needed xsi:type attribute on element
<anyType>
at weblogic.webservice.core.DefaultPart.toJava(DefaultPart.java:296)
at weblogic.webservice.core.DefaultMessage.toJava(DefaultMessage.java:35
9)
at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.jav
a:465)
at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.jav

Hi Daniel,
This is really an "constructing and XMLMap issue" with WebLogic Workshop, so I
would post it on that newsweb group:
weblogic.developer.interest.workshop
BTW: Serialization/Deserialization required instanciable classes with no-arg constructors.
You should attach the WSDL for this web service, so that folks can see what Workshop
generated for the schema element(s). This (the schema elements) is probably where
the problem starts :-) Also, state if that is the default xmlmap generated by
Workshop, or a custom one.
Regards,
Mike Wooten
"daniel" <[email protected]> wrote:
>
The followings exception is thrown when using the access a web service
using the
proxy jar.
The return xml contains
<debts xm:bind="debts is return.safaccount.debts">
<anyType xm:multiple="debt in return.safaccount.debts">{debt}</anyType>
</debts>
debts is a vector contains Serializable Object class.
How do you resolve this?
<Nov 14, 2002 2:36:27 PM ICT> <Error> <HTTP> <101019> <[ServletContext(id=553030
0,name=EAIService,context-path=/EAIService)] Servlet failed with IOException
java.rmi.RemoteException: web service invoke failed; nested exception
is:
javax.xml.soap.SOAPException: failed to deserialize xml:weblogic.xml.sch
ema.binding.DeserializationException: did not find needed xsi:type attribute
on
element <anyType>
javax.xml.soap.SOAPException: failed to deserialize xml:weblogic.xml.schema.bind
ing.DeserializationException: did not find needed xsi:type attribute
on element
<anyType>
at weblogic.webservice.core.DefaultPart.toJava(DefaultPart.java:296)
at weblogic.webservice.core.DefaultMessage.toJava(DefaultMessage.java:35
9)
at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.jav
a:465)
at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.jav

Differences between SOAP-ENV and soapenv

Hi all,
I am trying to find out why some SOAP request (inbound web services) in siebel work and do not work when the namespace prefix is SOAP-ENV and soapenv,
For example XML Spy generates "</SOAP-ENV:Envelope>" where as soapUI generates "<soapenv:Envelope>" and some difference in the name spaces.
Intrestingly other scenarios like invoking inbound web services with WS-Security and with out security had worked fine when tested from XML Spy.
Why is siebel not accepting the xml from XML Spy for Siebel Authentication scenario?
Thank you

Hi, just to let you all know, and please correct me if I am wrong, I have found this on the internet:
http://mail-archives.apache.org/mod_mbox/ws-axis-user/200308.mbox/%3C00fd01c35ba6$ed85e620$6f01a8c0@TPX21%3E
Although, the SOAP spec uses the namespace prefixes of SOAP-ENV and
SOAP-ENC, these prefixes aren't required. You can use any string you like as
a namespace prefix, just as long as it maps to the appropriate namespace
name. The reason why the spec bothers with telling us the notational
conventions is that prefix names (e.g., SOAP-ENV) aren't normative, and the
spec just happens to be using this set of naming conventions. So the prefix
name doesn't matter. Only the actual referenced namespace name (e.g.,
http://schema.xmlsoap.org/soap/envelope/) matters.
I confirmed this information from an expert from Fusion Middleware and he says that the name-prefix could be anything as long as it is mapped in the namespace (URL from the SOAP XML).

Problem in mapping while using Do not Use SOAP Envelope

Hi All,
This is wrt my thread 'Removing and adding SOAP Envelope'
I am currently working on SOAP-XI-Proxy Scenario.
For some un avoiadable reason, I had to use the option 'DO not use SOAP Envelope' .So the SOAP Envelope came withen the payload and in the pipeline, I can see the payload prefixed by '<?xml version="1.0" ?>' .
Now my payload looks like
<?xml version="1.0" ?> ( no more the encoding="utf-8" notation is there)
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
 xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Body>
<Complaint_Request xmlns="urn:******createserviceticket">
<CaseNo>12345</CaseNo>
<CustomerNo>12345</CustomerNo>
</Complaint_Request>
</soapenv:Body>
</soapenv:Envelope>
To accomodate the change, I also changed my request structure as
<Complaint_Request> (My new message Type)
 <Envelope>
 <Body>
 <Complaint_Request> (My previous message Type)
 <caseNo>
 <CustomerNo>
But I am facing problem in mapping the values to the target structure (which is a flat structure),
as the payload doesnot start with ' ns1: ' notation any more . Even XSLT mapping is not working.
When I am pasting the payload in the Testing Mapping Editor, the Source Node are correctly
formed, but all come in RED . But as the root node , ie 'ns0' is not there, the value
from child nodes are not getting mapped to the target fields.
Regards,
Subhendu

Hi Joel,
SAP says, when we use the option 'DO Not Use SOAP Envelope', the payload also contains the SOAP
Envelope. So it is obvious that the payload wont start with 'ns0' notation.
So I am searching for a solution, when we use that option.
Regards,
Subhendu

SOAPException: faultCode=SOAP-ENV:Protocol; msg=Missing content type

I have a WSDL file for which I have created a Web Service stub/skeleton through jdeveloper(version 10.1.2.3.0). Below is the complete code which has been generated by developer. Now whenever i try to run this file in jdeveloper I get the following exception. Please let me know how to resolve this issue.
Also error message is received at the following line of code:
*msg.send(endpointURL, ""<<some URL>>", requestEnv);*
{code}
*Exception Message*
{code}
[SOAPException: faultCode=SOAP-ENV:Protocol; msg=Missing content type.]
at org.apache.soap.transport.TransportMessage.read(TransportMessage.java:249)
at oracle.soap.transport.http.OracleSOAPHTTPConnection.post(OracleSOAPHTTPConnection.java:973)
at oracle.soap.transport.http.OracleSOAPHTTPConnection.send(OracleSOAPHTTPConnection.java:722)
at org.apache.soap.messaging.Message.send(Message.java:125)
at mypackage.NPVNSDLStub.PANDetails(NPVNSDLStub.java:88)
at mypackage.NPVNSDLStub.main(NPVNSDLStub.java:41)
{code}
*Code generated by Jdeveloper*
{code}
package mypackage;
import oracle.soap.transport.http.OracleSOAPHTTPConnection;
import org.apache.soap.encoding.SOAPMappingRegistry;
import org.w3c.dom.Element;
import java.util.Vector;
import oracle.jdeveloper.webservices.runtime.WrappedDocLiteralStub;
import java.net.URL;
import org.apache.soap.Envelope;
import org.apache.soap.Body;
import org.apache.soap.messaging.Message;
import java.util.Properties;
* Generated by the Oracle JDeveloper 10g Web Services Stub/Skeleton Generator.
* Date Created: Wed Feb 29 18:39:33 IST 2012
* WSDL URL: file:/C:/WS/sample.wsdl
public class NPVNSDLStub extends WrappedDocLiteralStub
public NPVNSDLStub()
m_httpConnection = new OracleSOAPHTTPConnection();
public static void main(String[] args)
try
NPVNSDLStub stub = new NPVNSDLStub();
stub.PANDetails("aaaaa8888a");
catch(Exception ex)
ex.printStackTrace();
private String _endpoint = "<<some URL>>";
public String getEndpoint()
return _endpoint;
public void setEndpoint(String endpoint)
_endpoint = endpoint;
private OracleSOAPHTTPConnection m_httpConnection = null;
private SOAPMappingRegistry m_smr = null;
public String PANDetails(String Request) throws Exception
URL endpointURL = new URL(_endpoint);
Envelope requestEnv = new Envelope();
Body requestBody = new Body();
Vector requestBodyEntries = new Vector();
String wrappingName = "PANValidationRequest";
String targetNamespace = "<<namespace url>>";
Vector requestData = new Vector();
requestData.add(new Object[] {"Request", Request});
requestBodyEntries.addElement(toElement(wrappingName, targetNamespace, requestData, false));
requestBody.setBodyEntries(requestBodyEntries);
requestEnv.setBody(requestBody);
Message msg = new Message();
msg.setSOAPTransport(m_httpConnection);
*msg.send(endpointURL, "<<some URL>>", requestEnv);*
Envelope responseEnv = msg.receiveEnvelope();
Body responseBody = responseEnv.getBody();
Vector responseData = responseBody.getBodyEntries();
return (String)fromElement((Element)responseData.elementAt(0), java.lang.String.class);
{code}
Edited by: EJP on 2/03/2012 17:22: added code tags, but your indentation needs fixing

Kishore,
See the links referenced in these threads.
Web Services and R12
Re: Web Services and R12
Integrated SOA Gateway
Re: Integrated SOA Gateway
Regards,
Hussein

Unsing RequestOneWayBean with Do Not Use SOAP Envelope

HI All ,
I have a requriement where Ecc is calling PI with an Asyn Proxy and PI calls a Sync Webservice and gets the Response back and sends the response back to ECC in Async manner . (Async - Sync Bridge).
I need to call aWeb Service which required specifc SOAP Headers . SO I have created a Custom Structure via XSLT mapping and calling the Web Service with the Option Do Not Use SOAP Envelope as checked . I have also used the RequestResponse Bean & ResponseOneWay Bean in the SOAP Receiver adapter to make the call from Sync to Asyn. When I execute the Interface the response from the Web Service is not flowing into PI .
I am getting the error "Exception caught by adapter framework: InterfaceDetermination did not yield any actual interface" .
Has anyone worked on the ResponseOneway Bean with parameter "Do Not Use SOAP Envelope as checked" . Can some one please help me out with this issue..
Thanks
Regards
NIlesh Taunk.

HI Eng ,
I have not been able to accept the SOAP Fault Response. The link that you have provided above works for accepting the SOAP Fault . But in my case the SOAP Receiver Adapter has the Option "DO NOT Use SOAP Envelope " checked . So it is still not working in my case .
I have made all the Configurations in the Receiver SOAP adapter but am unable to get the fault response back .
Please find below the Screenshot of the Receiver SOAP Adapter.
Im my case I am able to receive the successfull response in my Response Mappping (I have created a diff ICO for Response Message and a diff ICO for Fault Message). When a fault is received even the Fault message goes to the response mapping and it fails in the response mapping as the fault structure & the response structure do not match .
Do we need to make some additional configuration for the handing faults, whn the option "DO NOT use SOAP envlope is checked" as it removed the Env from the messgaes.
Am I missing something, would you be able to have a look.
Thanks
Regards
Nilesh Taunk.

SOAP Adapter: DO not use soap envelope

Hi Guys
I have a scenario, which calls a webservice from my ABAP Proxies, the twist in this is that SOAP request expects license info into the header of SOAP envelope, I could achive this by XSLT mapping in the receiver SOAP adapter I selected the option "Do not use SOAP envelope" and could do the call.
Due to this the response received from the webservice is treated as payload, as shown below...
response message payload:
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<Header xmlns="http://schemas.xmlsoap.org/soap/envelope/">
 <SubscriptionInfo xmlns="http://ws.strikeiron.com">
 <LicenseStatusCode>0</LicenseStatusCode>
 <LicenseStatus>Valid license key</LicenseStatus>
 <LicenseActionCode>0</LicenseActionCode>
 <LicenseAction>Decremented hit count</LicenseAction>
 <RemainingHits>18</RemainingHits>
 <Amount>0</Amount>
 </SubscriptionInfo>
</Header>
<soap:Body>
 <getRateResponse xmlns="CurrencyRates">
 <getRateResult>44.945</getRateResult>
 </getRateResponse>
</soap:Body>
</soap:Envelope>
and when i am trying to do the response mapping, it is not able to read the value.
Anyone having any idea, on how we could do this.
Thanks
Dheeraj

Hi
I am sorry for replying in so late, was busy with some projects.
I got few mails and this post is cathing up again, so thought of giving the solution I followed without any adapter module or anything, simple plain XSLT mapping.
Integration Repository
1. Created data type and message type for Outbound Interface
2. Imported the WSDL
3. Created an XSD out of the sample response I got by calling the WSDL (this you can do from any tool available, i used the strikeiron website), pls refer below to see the XSD below, and you will have to use the message type envelope from it.
4. Most Important step, created 2 XSLT mappings, one for request and the other for response., Pls refer below for both these mappings.
5. did the interface mapping
Integration Directory
1. pls configure your scenario as normaly you do, and while you configure the communication channel for your soap receiver, make sure you click on the do not use soap envelop option.
thats it done.
XSLT Request Mapping
<?xml version="1.0"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
 <xsl:template match="/">
 <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
 <SOAP-ENV:Header>
 <LicenseInfo xmlns="http://ws.strikeiron.com">
 <RegisteredUser>
 <UserID>xyz</UserID>
 <Password>xyz</Password>
 </RegisteredUser>
 </LicenseInfo>
 </SOAP-ENV:Header>
 <SOAP-ENV:Body>
 <getConversion xmlns="CurrencyRates">
 <FromCurrencyCode>
 <xsl:value-of select="//fromCurrency"/>
 </FromCurrencyCode>
 <ToCurrencyCode>
 <xsl:value-of select="//ToCurrency"/>
 </ToCurrencyCode>
 <Amount>1</Amount>
 </getConversion>
 </SOAP-ENV:Body>
 </SOAP-ENV:Envelope>
 </xsl:template>
</xsl:stylesheet>
XSLT Response Mapping
<?xml version='1.0' ?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:a="CurrencyRates" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
 <xsl:template match="/">
 <ns0:MT_Cur_res xmlns:ns0="http://www.april.in/WebService/SOAPHeader">
 <Rate>
 <xsl:value-of select="soap:Envelope/soap:Body/a:getConversionResponse/a:getConversionResult"/>
 </Rate>
 </ns0:MT_Cur_res>
 </xsl:template>
</xsl:stylesheet>
Webservice Response XSD
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" targetNamespace="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns1="http://ws.strikeiron.com" xmlns:ns2="CurrencyRates">
<xs:import namespace="CurrencyRates" schemaLocation="ns2.xsd"/>
<xs:import namespace="http://ws.strikeiron.com" schemaLocation="ns1.xsd"/>
<xs:element name="Envelope">
 <xs:complexType>
 <xs:sequence>
 <xs:element ref="soap:Header"/>
 <xs:element ref="soap:Body"/>
 </xs:sequence>
 </xs:complexType>
</xs:element>
<xs:element name="Header">
 <xs:complexType>
 <xs:sequence>
 <xs:element ref="ns1:SubscriptionInfo"/>
 </xs:sequence>
 </xs:complexType>
</xs:element>
<xs:element name="Body">
 <xs:complexType>
 <xs:sequence>
 <xs:element ref="ns2:getConversionResponse"/>
 </xs:sequence>
 </xs:complexType>
</xs:element>
</xs:schema>
let me know in case somebody gets stuck somewhere for this scenario.
Take Care
Dheeraj

SOAP scenario "Do not use SOAP Envelope" check problems

Hi Gurus!
I'm again here.
I've an scenario with SOAP Receiver, the WS do I need consume, looks like:
POST /SumTotalws1/services/Authentication.asmx HTTP/1.1
Host: xxx.xxx.xxx.xxx
Content-Type: text/xml; charset=utf-8
Content-Length: length
SOAPAction: "http://www.sumtotalsystems.com/sumtotal7/sumtotalws/Authentication/Login"
<?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>
 <Login xmlns="http://www.sumtotalsystems.com/sumtotal7/sumtotalws/Authentication/">
 <credentials>
 <Username>string</Username>
 <Passcode>string</Passcode>
 <AuthenticationType>NotSpecified or Anonymous or NTAuthentication or Passport or LDAP</AuthenticationType>
 <AccountType>NotSpecified or WebService or WebUI</AccountType>
 </credentials>
 </Login>
</soap:Body>
</soap:Envelope>
but the response looks like:
HTTP/1.1 200 OK
Content-Type: text/xml; charset=utf-8
Content-Length: length
<?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:Header>
 <UserToken xmlns="http://www.sumtotalsystems.com/sumtotal7/sumtotalws/">
 <Value>string</Value>
 </UserToken>
</soap:Header>
<soap:Body>
 <LoginResponse xmlns="http://www.sumtotalsystems.com/sumtotal7/sumtotalws/Authentication/" />
</soap:Body>
</soap:Envelope>
when I create my communication channel with "Do not Use SOAP Envelope" uncheck it, all run ok, but I only get in response message "<LoginResponse>" and I need <UserToken>
When I check it "Do not use SOAP Envelope" and I use XSLT mapping to add SOAP Env to request message, I get response message empty.
I tried the web Service with the message that I obtained from de XSLT mapping in the program SOAPUI. I get ok response with the <UserToken> value.
some idea to solve this problem??
Thanks in advance.
Edited by: KrlosRios on Sep 30, 2011 8:07 PM

Hi, thanks for your answer.
Can I use AXIS to execute any WS?
The WS that I tried execute looks like this:
POST /xxxx/services/Authentication.asmx HTTP/1.1
Host: xxx.240.106.39
Content-Type: text/xml; charset=utf-8
Content-Length: length
SOAPAction: "http://xxx/Authentication/Login"
<?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>
 <Login xmlns="http://xxxxAuthentication/">
 <credentials>
 <Username>string</Username>
 <Passcode>string</Passcode>
 <AuthenticationType>NotSpecified or Anonymous or NTAuthentication or Passport or LDAP</AuthenticationType>
 <AccountType>NotSpecified or WebService or WebUI</AccountType>
 </credentials>
 </Login>
</soap:Body>
</soap:Envelope>
and for the response:
HTTP/1.1 200 OK
Content-Type: text/xml; charset=utf-8
Content-Length: length
<?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:Header>
 <UserToken xmlns="http://www.sumtotalsystems.com/sumtotal7/sumtotalws/">
 <Value>string</Value>
 </UserToken>
</soap:Header>
<soap:Body>
 <LoginResponse xmlns="http://www.sumtotalsystems.com/sumtotal7/sumtotalws/Authentication/"></LoginResponse>
</soap:Body>
</soap:Envelope>
also I found in Trace node in SXI_MONITOR, jus before execute response mapping :
<Trace level="1" type="B" name="PLSRV_MAPPING_RESPONSE"></Trace>
<Trace level="1" type="Timestamp">2011-11-01T19:33:34Z UTC-6 Start of pipeline service processing PLSRVID= PLSRV_MAPPING_RESPONSE</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="3" type="T">Calling pipeline service: PLSRV_MAPPING_RESPONSE</Trace>
<Trace level="3" type="T">Reading Pipeline-Service specification... </Trace>
<Trace level="3" type="T">PLSRVTYPE = </Trace>
<Trace level="3" type="T">ADRESSMOD = LOCAL</Trace>
<Trace level="3" type="T">P_CLASS = CL_MAPPING_XMS_PLSRV3</Trace>
<Trace level="3" type="T">P_IFNAME = IF_XMS_PLSRV</Trace>
<Trace level="3" type="T">P_METHOD = ENTER_PLSRV</Trace>
<Trace level="3" type="T"> </Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL"></Trace>
<Trace level="1" type="B" name="CL_MAPPING_XMS_PLSRV3-ENTER_PLSRV"></Trace>
<Trace level="2" type="T">......attachment XI_Context not found </Trace>
<Trace level="3" type="T">Das Mapping wurde bereits in der Interface-Ermittlung bestimmt. </Trace>
<Trace level="3" type="T">Objekt-Id des Interface-Mappings 8594D8C2E6DA3C008F45B112FFCC86B8 </Trace>
<Trace level="3" type="T">Versions-Id des Interface-Mappings C3BB8FB0A1D511E0A688E9FCB9F06E16 </Trace>
<Trace level="1" type="T">Interface-Mapping http://xxxxx.net/pi/lms/Authentication OM_LMS_Authentication </Trace>
<Trace level="3" type="T">Mapping-Schritte 1 XSLT Response_LMS_Auth5 </Trace>
<Trace level="3" type="T">MTOM-Attachments werden nicht in die Payload überführt. </Trace>
<Trace level="1" type="T">Payload is empty. </Trace>
<Trace level="3" type="T">Dynamische Konfiguration ist leer. </Trace>
<Trace level="2" type="T">Modus 0 </Trace>
<Trace level="2" type="T">Call XSLT processor with stylsheet Response_LMS_Auth5.xsl. </Trace>
<Trace level="3" type="T">Method fatalError called, terminate transformation, because of
Thrown:
javax.xml.transform.TransformerException: java.io.IOException: Parsing an empty source. Root element expected!
 at com.sap.engine.lib.jaxp.TransformerImpl.transform(TransformerImpl.java:250)
Say Payload is empty.
and in left directory tree, not exist "payload" node, only existe SOAP Body and in "Manifest" node looks like this:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

<SAP:Manifest wsu:Id="wsuid-manifest-5CABE13F5C59AB7FE10000000A1551F7" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:wsu="http://www.docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
<SAP:Payload xlink:href="cid:att-60c3078b066911e1bc1500000093b25a @sap.com">
<SAP:Name>MainAttachment</SAP:Name><
SAP:Description>Main document</SAP:Description>
<SAP:Type>Application</SAP:Type></SAP:Payload>
</SAP:Manifest>
Thanks for your help.

OSB not adding SOAP-ENV:encodingStyle attribute, invoke fails

Similar Messages

Maybe you are looking for