SOAP response customize body

Hi,
I have created the sample "Stateless Java Web Service Tutorial" HelloImpl.java
My SOAP response contains the follwoing tag
<ns1:sayHelloReponse xmlns="..." SOAP-ENV="...">
<return xsi:type="string">Hello Test! The ... </return>
</ns1:sayHelloResponse>
I want the soap message not to print the return tag as string but my custom tag which is an xml file, i want my class to return an xml formatted string and the xml will be my reponse
please advice

well..the problem is..the db adapter has it's own transaction..so the transactions fails or not.
you're just not capable of checking if the transaction went ok...and return 'process completed ok' or when the transaction failed for some reason return 'the process aborted'.
So you just need some extra steps for it to be able to return some response-message

Similar Messages

BPEL process to create a PDF and send it as attachment in SOAP response

We have a requirement to have a webservice created using BPEL, which can receive input from a client and create a PDF using the input and send the PDF as attachment in the SOAP response.
We have found the below link in Oracle docs and our basic understanding on the functionality given is that the MIMEService is being used to read a SOAP attachment from some other service and send it as an attachment in the SOAP response to the requester. As explained above, this doesn't completely satisfy our requirement.
http://docs.oracle.com/cd/E11036_01/integrate.1013/b28981/manipdoc.htm#BABCJIAH
Please suggest if there is any other approach that suites our requirement.
Thanks.

Hi,
I have a Weblogic webservice which returns me a PDF attachment as resposne ( here I have MIME related stuff).I need to get attachment as bpel response.
I have created a BPEL process to invoke the weblogic webservice. I have explictly added the MIME part in bpel.wsdl same as weblogic webservice wsdl.
I tried to assign the response variable( of type base64binary) of bpel.wsdl and my webservice .wsdl . I am getting some error with no attachment.
Below is my xsd used in BPEL.wsdl*
<?xml version="1.0" encoding="UTF-8"?>
<schema attributeFormDefault="unqualified"
 elementFormDefault="qualified"
 targetNamespace="http://xmlns.oracle.com/MIMEApp/test/BPELProcess1"
 xmlns="http://www.w3.org/2001/XMLSchema">
 <complexType name="process">
 <sequence>
 <element name="input" type="string"/>
 </sequence>
 </complexType>
 <complexType name="processResponse">
 <sequence>
 <element name="result" type="string"/>
 </sequence>
 </complexType>
<complexType name="GetAttachmentPDF">
<sequence>
<element minOccurs="0" name="Pdf" nillable="false" type="base64Binary"/>
</sequence>
</complexType>
</schema>
Below is my BPEL.wsdl*
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions name="BPELProcess1"
targetNamespace="http://xmlns.oracle.com/MIMEApp/test/BPELProcess1"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:client="http://xmlns.oracle.com/MIMEApp/test/BPELProcess1"
xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/">

<wsdl:types>
<schema xmlns="http://www.w3.org/2001/XMLSchema">
<import namespace="http://xmlns.oracle.com/MIMEApp/test/BPELProcess1"
schemaLocation="xsd/BPELProcess1.xsd"/>
</schema>
</wsdl:types>

<wsdl:message name="BPELProcess1RequestMessage">
<wsdl:part name="payload" type="client:process"/>
</wsdl:message>
<wsdl:message name="BPELProcess1ResponseMessage">
<wsdl:part name="payload" type="client:processResponse"/>
<wsdl:part name="attachment" type="client:GetAttachmentPDF"/>
</wsdl:message>


<wsdl:portType name="BPELProcess1">
<wsdl:operation name="process">
<wsdl:input message="client:BPELProcess1RequestMessage"/>
<wsdl:output message="client:BPELProcess1ResponseMessage"/>
</wsdl:operation>
</wsdl:portType>

<plnk:partnerLinkType name="BPELProcess1">
<plnk:role name="BPELProcess1Provider">
<plnk:portType name="client:BPELProcess1"/>
</plnk:role>
</plnk:partnerLinkType>
<wsdl:binding name="BPELProcess1SOAP11Binding" type="client:BPELProcess1">
<soap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="process">
<soap:operation style="rpc"
soapAction="http://xmlns.oracle.com/MIMEApp/test/BPELProcess1/process"/>
<wsdl:input>
<soap:body use="literal"
namespace="http://xmlns.oracle.com/MIMEApp/test/BPELProcess1"/>
</wsdl:input>
<wsdl:output>
<mime:multipartRelated>
<mime:part>
<soap:body use="literal"
namespace="http://xmlns.oracle.com/MIMEApp/test/BPELProcess1"/>
</mime:part>
<mime:part>
<mime:content part="attachment" type="application/pdf"/>
</mime:part>
</mime:multipartRelated>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
</wsdl:definitions>
Below is my WL WS WSDL*
<?xml version="1.0" encoding="UTF-8"?>
<WL5G3N0:definitions
name="NewWSDLFile"
targetNamespace="http://www.example.org/NewWSDLFile/"
xmlns:WL5G3N5="http://schemas.xmlsoap.org/wsdl/mime/"
xmlns:WL5G3N4="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:WL5G3N3="http://www.example.org/NewWSDLFile/"
xmlns:WL5G3N2="java:com.rogers.service"
xmlns:WL5G3N0="http://schemas.xmlsoap.org/wsdl/"
xmlns:WL5G3N1="http://www.w3.org/2001/XMLSchema"
>
<WL5G3N0:types>
<xsd:schema attributeFormDefault="unqualified" elementFormDefault="qualified" targetNamespace="java:com.rogers.service"
xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:s="java:com.rogers.service"
xmlns:s0="http://schemas.xmlsoap.org/wsdl/" xmlns:s1="http://www.w3.org/2001/XMLSchema"
xmlns:s2="java:com.rogers.service" xmlns:s3="http://www.example.org/NewWSDLFile/"
xmlns:s4="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:s5="http://schemas.xmlsoap.org/wsdl/mime/"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://www.example.org/NewWSDLFile/"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:complexType name="GetAttachmentPDF">
<xsd:sequence>
<xsd:element minOccurs="0" name="Pdf" nillable="false" type="xs:base64Binary"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="GetAttachmentResult">
<xsd:sequence>
<xsd:element minOccurs="1" name="Message" nillable="true" type="xs:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>
</WL5G3N0:types>
<WL5G3N0:message name="NewOperationRequest">
<WL5G3N0:part name="GetAttachment" type="WL5G3N1:string"/>
</WL5G3N0:message>
<WL5G3N0:message name="NewOperationResponse">
<WL5G3N0:part name="NewOperationResponse" type="WL5G3N2:GetAttachmentResult"/>
<WL5G3N0:part name="attachment" type="WL5G3N2:GetAttachmentPDF"/>
</WL5G3N0:message>
<WL5G3N0:portType name="NewWSDLFile">
<WL5G3N0:operation name="NewOperation">
<WL5G3N0:input message="WL5G3N3:NewOperationRequest"/>
<WL5G3N0:output message="WL5G3N3:NewOperationResponse"/>
</WL5G3N0:operation>
</WL5G3N0:portType>
<WL5G3N0:binding name="NewWSDLFileSOAP" type="WL5G3N3:NewWSDLFile">
<WL5G3N4:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
<WL5G3N0:operation name="NewOperation">
<WL5G3N4:operation soapAction="http://www.example.org/NewWSDLFile/NewOperation"/>
<WL5G3N0:input>
<WL5G3N4:body use="literal" namespace="http://www.example.org/NewWSDLFile/"/>
</WL5G3N0:input>
<WL5G3N0:output>
<WL5G3N5:multipartRelated>
<WL5G3N5:part>
<WL5G3N4:body use="literal" namespace="http://www.example.org/NewWSDLFile/"/>
</WL5G3N5:part>
<WL5G3N5:part>
<WL5G3N5:content part="attachment" type="application/pdf"/>
</WL5G3N5:part>
</WL5G3N5:multipartRelated>
</WL5G3N0:output>
</WL5G3N0:operation>
</WL5G3N0:binding>
<WL5G3N0:service name="NewWSDLFile">
<WL5G3N0:port name="NewWSDLFileSOAP" binding="WL5G3N3:NewWSDLFileSOAP">
<WL5G3N4:address location="http://localhost:7001/something/NewWSDLFileImpl"/>
</WL5G3N0:port>
</WL5G3N0:service>
</WL5G3N0:definitions>
I refered the below link:
http://docs.oracle.com/cd/B14099_19/integrate.1012/b14448/manipdoc.htm.
4.16.1.1 WSDL File Contents
They are using ra:writeBinaryToFile() and ora:ReadBinaryFromFile(). I couldnt get a proper sample to understand the use of these functions.
Please advise.
Regards
Ipsita

Oracle ESB 10g : Blank namespace in the SOAP Response from DB adapter

Hi All,
I am currently working on a ESB project to route input XML file as a parameter to a DB Function.
This Function has a input parameter of type XMLTYPE and returns VARCHAR2 values.
I have configured the DB Adapter to invoke this function and return the result as a SOAP response.
The WSDL of DB adapter contains XML_DATA as input and XMLMAIN as the output result.
The ESB project works fine as expected. But in the result from DB adapter contains a blank namespace [xmlns=""] for the XMLMAIN element .
I hereby attach the output XML.
Please help how to remove this blank namespace from the output.
We are using SOA Suite 10g 10.1.3.5
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<env:Header/>
<env:Body xmlns="http://xmlns.oracle.com/pcbpel/adapter/db/XXWEB/XMLMISCRCPTINSERTPKG/XMLMAIN/">
<OutputParameters xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<XMLMAIN xmlns="">100</XMLMAIN>
</OutputParameters>
</env:Body>
</env:Envelope>
Thanks and Regards,
Justin Michael Raj

well..the problem is..the db adapter has it's own transaction..so the transactions fails or not.
you're just not capable of checking if the transaction went ok...and return 'process completed ok' or when the transaction failed for some reason return 'the process aborted'.
So you just need some extra steps for it to be able to return some response-message

SOAP Response change from http 200 to http 204

Hello
I must change for a application, that call a webservice on the pi, change the
SOAP Response from HTTP 200 OK to HTTP 204. I think that must chnage on the SOAP Adapter and wei can't change in the messages or mapping. Also wit a Fault Messages is this not runnig.
What is with BPM, have any body do somthing with that.
Regards Tom

Hello Stefan
This thrid Application need this response. We cann't change this. We spaek with this product manager, but he want change this. He want this when the interface is async, that application now no conntent come back.
Regards Tom

Soap response with envelope

Hi
My PI server is able to make a soap call to the SFDC ( webservice ) ...however the response that is received within PI
has a SOAP envelope...and hence the response mapping is going in error....because the source data type in response mapping doesnot match with the soap response ( with envelope )
<?xml version="1.0" encoding="UTF-8" ?>
- <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns="urn:enterprise.soap.sforce.com">
- <soapenv:Body>
- <upsertResponse>
- <result>
<created>false</created>
<id>a0UT0000004aeaMMAQ</id>
<success>true</success>
</result>
</upsertResponse>
</soapenv:Body>
</soapenv:Envelope>
how do i handle this

Hi,
I think there is an option while configuration of SOAP adapter, where you can define, not to keep SOAP envelop. Please check the option Conversion Parameters\Do Not Use SOAP Envelope and set it as per your requirement. That might solve the problem. Here is the link which can be helpful
http://help.sap.com/saphelp_nw04/helpdata/en/29/5bd93f130f9215e10000000a155106/content.htm
Alternatively you need a java mapping or XSLT mapping to remove the envelop.
Here is the java mapping code to remove SOAP envelop
import java.io.FileInputStream;
import java.io.FileOutputStream;
import java.io.InputStream;
import java.io.OutputStream;
import java.util.Map;
import javax.xml.parsers.DocumentBuilder;
import javax.xml.parsers.DocumentBuilderFactory;
import javax.xml.transform.Transformer;
import javax.xml.transform.TransformerFactory;
import javax.xml.transform.dom.DOMSource;
import javax.xml.transform.stream.StreamResult;
import org.w3c.dom.Document;
import org.w3c.dom.Element;
import org.w3c.dom.Node;
import org.w3c.dom.NodeList;
import com.sap.aii.mapping.api.StreamTransformation;
import com.sap.aii.mapping.api.StreamTransformationException;
public class RemoveSoapEnvelop implements StreamTransformation{
public void execute(InputStream in, OutputStream out)
throws StreamTransformationException {
try
 DocumentBuilderFactory factory=DocumentBuilderFactory.newInstance();
 DocumentBuilder builderel=factory.newDocumentBuilder();
 /*input document in form of XML*/
 Document docIn=builderel.parse(in);
 /*document after parsing*/
 Document docOut=builderel.newDocument();
 TransformerFactory tf=TransformerFactory.newInstance();
 Transformer transform=tf.newTransformer();
 Element root;
 Node p;
 NodeList l;
 int mm,n1;
 //if you need to include namespace use next two lines
 //root=docOut.createElement("ns0:upsertResponse");
 //root.setAttribute("xmlns:ns0","http://connectsystems.be/MAINFR/AccDocument");
 root=docOut.createElement("upsertResponse");
 p=docIn.getElementsByTagName("upsertResponse").item(0);
 l=p.getChildNodes();
 n1=l.getLength();
 for(mm=0;mm<n1;++mm)
 Node temp=docOut.importNode(l.item(mm),true);
 root.appendChild(temp);
 docOut.appendChild(root);
 transform.transform(new DOMSource(docOut), new StreamResult(out));
catch(Exception e)
 e.printStackTrace();
public void setParameter(Map arg0) {
public static void main(String[] args) {
try{
 RemoveSoapEnvelop genFormat=new RemoveSoapEnvelop();
 FileInputStream in=new FileInputStream("C:\\Apps\\my folder\\sdn\\sd2.xml");
 FileOutputStream out=new FileOutputStream("C:\\Apps\\my folder\\sdn\\removedEnvelop.xml");
 genFormat.execute(in,out);
catch(Exception e)
e.printStackTrace();
input xml file sd2.xml
<?xml version="1.0" encoding="UTF-8" ?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns="urn:enterprise.soap.sforce.com">
<soapenv:Body>
<upsertResponse>
<result>
<created>false</created>
<id>a0UT0000004aeaMMAQ</id>
<success>true</success>
</result>
</upsertResponse>
</soapenv:Body>
</soapenv:Envelope>
Here is the output xml removedEnvelop.xml
<?xml version="1.0" encoding="UTF-8" ?>
<upsertResponse>
<result>
<created>false</created>
<id>a0UT0000004aeaMMAQ</id>
<success>true</success>
</result>
</upsertResponse>
Helpful articles on java mapping for PI 7.1
http://wiki.sdn.sap.com/wiki/display/XI/SampleJAVAMappingcodeusingPI7.1+API
You can also try following XSLT mapping to get the same output as java mapping
<xsl:stylesheet version="1.0"
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
exclude-result-prefixes="SOAP-ENV">
<xsl:output method="xml" version="1.0" encoding="UTF-8" indent="yes" />
<xsl:template match="/">
<xsl:for-each select="SOAP-ENV:Envelope/SOAP-ENV:Body">
<upsertResponse>
<result>
 <xsl:variable name="var" select="normalize-space(.)"></xsl:variable>
 <xsl:variable name="tokenizedSample" select="tokenize($var,' ')"/>
 <created><xsl:value-of select="$tokenizedSample[1]"/></created>
 <id><xsl:value-of select="$tokenizedSample[2]"/></id>
 <success><xsl:value-of select="$tokenizedSample[3]"/></success>
</result>
</upsertResponse>
</xsl:for-each>
</xsl:template>
</xsl:stylesheet>
Other than these please refer to following links for further examples on the topic
Remove SOAP-ENV tags from xml RECEIVER RESPONSE payload (XSL needed?)
Remove SOAP Envelop using XSLT mapping.
Hope this helps your cause.
regards
Anupam

Presence of multiref tag in soap response message

We are having a problem when we try to call a web service in PI. The web services called is provided by an Axis server.
We tried to use the plain HTTP protocol in the definition of the communication channel as shown here:
Adapter type: SOAP
Transport protocol: HTTP
Message protocol: SOAP 1.1
Adapter engine: Central Adapter Engine
We got the followong error response in SXMB_MONI:
The payload shown in SXNB_MONI is:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

<ns1:cedstr_obt_cle_elem_v2_Response xmlns:ns1='urn:CEDSTR' soapenv:encodingStyle='http://schemas.xmlsoap.org/soap/encoding/' 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'>
<tab_cle soapenc:arrayType='ns1:cedstr_cle_elem_v1[3]' xmlns:soapenc='http://schemas.xmlsoap.org/soap/encoding/' xsi:type='soapenc:Array'>
<item href='#id0'/>
<item href='#id1'/>
<item href='#id2'/>
</tab_cle><nb_cle xsi:type='xsd:int'>3</nb_cle><stat_elem href='#id3'/>
<cdr href='#id4'/>
</ns1:cedstr_obt_cle_elem_v2_Response>
The expected payload is:
<?xml version="1.0" encoding="UTF-8" ?>
- <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>
- <ns1:cedstr_obt_cle_elem_v2_Response soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns1="urn:CEDSTR">
- <tab_cle xsi:type="soapenc:Array" soapenc:arrayType="ns1:cedstr_cle_elem_v1[3]" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">
<item href="#id0" />
<item href="#id1" />
<item href="#id2" />
</tab_cle>
<nb_cle xsi:type="xsd:int">3</nb_cle>
<stat_elem href="#id3" />
<cdr href="#id4" />
</ns1:cedstr_obt_cle_elem_v2_Response>
- <multiRef id="id0" soapenc:root="0" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xsi:type="ns2:cedstr_cle_elem_v1" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns2="urn:CEDSTR">
<id_structure_det xsi:type="xsd:int">118406</id_structure_det>
<ordinal xsi:type="xsd:int">2648545</ordinal>
<appareil xsi:type="xsd:string">C3D1E</appareil>
<type_cable xsi:type="xsd:string">H</type_cable>
</multiRef>
- <multiRef id="id1" soapenc:root="0" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xsi:type="ns3:cedstr_cle_elem_v1" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns3="urn:CEDSTR">
<id_structure_det xsi:type="xsd:int">984806</id_structure_det>
<ordinal xsi:type="xsd:int">2723425</ordinal>
<appareil xsi:type="xsd:string">O5C3X</appareil>
<type_cable xsi:type="xsd:string">H</type_cable>
</multiRef>
- <multiRef id="id2" soapenc:root="0" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xsi:type="ns4:cedstr_cle_elem_v1" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns4="urn:CEDSTR">
<id_structure_det xsi:type="xsd:int">1163686</id_structure_det>
<ordinal xsi:type="xsd:int">3144641</ordinal>
<appareil xsi:type="xsd:string">Y0A6B</appareil>
<type_cable xsi:type="xsd:string">H</type_cable>
</multiRef>
- <multiRef id="id3" soapenc:root="0" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xsi:type="ns5:cedstr_stat_elem_v1" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns5="urn:CEDSTR">
<tension xsi:type="xsd:string">MT</tension>
<nb_concess xsi:type="xsd:int">0</nb_concess>
<nb_restr xsi:type="xsd:int">0</nb_restr>
<localisation xsi:type="xsd:string">DEVILLERS EST DE BEAUREGARD</localisation>
<remarque xsi:type="xsd:string" />
</multiRef>
- <multiRef id="id4" soapenc:root="0" soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xsi:type="ns6:utlgen_cdr" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns6="urn:CEDSTR">
<succes xsi:type="xsd:int">1</succes>
<code xsi:type="xsd:int">0</code>
<message xsi:type="xsd:string" />
</multiRef>
</soapenv:Body>
</soapenv:Envelope>
</ns1:cedptr_obt_cle_di_v1_HResponse>
What I can see is that PI seems to ignore the multiref tag in the SOAP response message. Does anybody knows if there is an issue with the mutiref tag in PI ?
Thanks for your help.

The SOAP adapter does not support more than one body child.
If a SOAP message with several body childs arrive, then only the first body child is considered, all other body childs are ignored.
Regards
Stefan

Xsl/stylesheet transformation problem in soap response(usinf xmlx-tags.tld)

Hi,
I have problem in transforming the soap response using xmlx-tags.tld.....
I was not able to read the <EmpName> value from the returned xml...
The stylesheet / xsl does not return any elements if I use other then "/" in match
attribute : <xsl:template match="/">
here is my soap call and stylesheet in JSP:
<x:xslt media="html">
<x:xml>
<ws:soap ttl="360000">
<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>
... making soap call here...
</soap:Body>
</soap:Envelope>
</ws:soap>
</x:xml>
<x:stylesheet media="html">
<xsl:stylesheet version='1.0' xmlns:xsl='http://www.w3.org/1999/XSL/Transform'>
<xsl:output method="xmll" omit-xml-declaration="no"
doctype-public="-//W3C//DTD HTML 4.0 Transitional//EN" indent="yes" />
<xsl:template match="GetEmpResult">
<html>
<body>
Result: Symbol <xsl:value-of select="EmpName"/>
</body
</html>
</xsl:stylesheet>
</x:stylesheet>
</x:xslt>
the SOAP response looks like this:
<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>
<GetEmpResponse xmlns="http://ws.cdyne.com/">
<GetEmpResult>
<EmpID>string</EmpID>
<EmpName>string</EmpName>
<SalAmount>decimal</SalAmount>
<Error>boolean</Error>
</GetEmpResult>
</GetEmpResponse>
</soap:Body>
</soap:Envelope>
I tried all the possibilities of template matches, but not succeeded....
Can somebody help me the correct <xsl:template> to access EmpName from the above
SOAP responses...
regards
Vijay

Hi,
Dynamic xslt are not quite supported in OSB, there are some approaches that may be helpful for your case though...
Have a look at these...
http://atheek.wordpress.com/2011/12/21/using-xalanevaluate-to-parametrize-xpath/
http://beatechnologies.wordpress.com/2010/12/01/dynamic-xquery-in-oracle-service-bus/
Let me know how you go...
Cheers,
Vlad

SOAP: response message contains an error

Hi,
I send a message by PI to a service and I get the following message:
SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: No such operation SETCOMPANYFIELDVALUERequest
The scenario that I use is a RFC --> PI --> SOAP. The WSDL looks like this:
<?xml version="1.0" encoding="UTF-8"?>
<wsdl:definitions targetNamespace="urn:DefaultNamespace" xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:apachesoap="http://xml.apache.org/xml-soap" xmlns:impl="urn:DefaultNamespace" xmlns:intf="urn:DefaultNamespace" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<wsdl:message name="SETCOMPANYFIELDVALUERequest">
<wsdl:part name="COMPANYNAME1" type="xsd:string"/>
<wsdl:part name="COMPANYNAME2" type="xsd:string"/>
</wsdl:message>
<wsdl:message name="SETCOMPANYFIELDVALUEResponse">
<wsdl:part name="SETCOMPANYFIELDVALUEReturn" type="xsd:anyType"/>
</wsdl:message>
<wsdl:portType name="AppLSDataSync">
<wsdl:operation name="SETCOMPANYFIELDVALUE" parameterOrder="COMPANYNAME1 COMPANYNAME2">
 <wsdl:input message="intf:SETCOMPANYFIELDVALUERequest" name="SETCOMPANYFIELDVALUERequest"/>
 <wsdl:output message="intf:SETCOMPANYFIELDVALUEResponse" name="SETCOMPANYFIELDVALUEResponse"/>
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="DominoSoapBinding" type="intf:AppLSDataSync">
<wsdlsoap:binding style="rpc" transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="SETCOMPANYFIELDVALUE">
 <wsdlsoap:operation soapAction="SETCOMPANYFIELDVALUE"/>
 <wsdl:input name="SETCOMPANYFIELDVALUERequest">
 <wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:DefaultNamespace" use="encoded"/>
 </wsdl:input>
 <wsdl:output name="SETCOMPANYFIELDVALUEResponse">
 <wsdlsoap:body encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" namespace="urn:DefaultNamespace" use="encoded"/>
 </wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="AppLSDataSyncService">
<wsdl:port binding="intf:DominoSoapBinding" name="Domino">
 <wsdlsoap:address location="http://localhost"/>
</wsdl:port>
</wsdl:service>
</wsdl:definitions>
When I send the same message using the WebServiceNavigator everything is working fine.
The WSDL that I have imported into PI is the same that is available that I use calling by the WSNavigator.
Anyone an Idea?
Thanks Ron

HI
WSDL is having some problem
When you imported this wsdl how many messages does it show. Check weather it is having SETCOMPANYFIELDVALUE request and response. you can check the messages carried in a wsdl using the messages tab in external definition.
Thanks

Weblogic throwing "null SOAP element Exception" in multi-part SOAP response

Hi All,
I'm using weblogic 10. My application is a webservice client generated using '*clientgen*', which is running on weblogic, and
is invoking a remotely hosted webservice ( Remotely hoseted webservice may not be running on weblogic).
I've the wsdl file of remotely hosted webservice.
Now the problem is with WSDL file (I suppose), have a look at this.
*<message name="m1">*
*<part name="body" element="tns:GetCompanyInfo"/>*
*</message>*
*<message name="m2">*
*<part name="body" element="tns:GetCompanyInfoResult"/>*
*<part name="docs" type="xsd:AnyComplexType"/> ------> assume all elements inside this complex type can be nil or minOccurs set to '0'*
*<part name="logo" type="xsd:AnyOtherComplexType"/> ------> assume all elements inside this complex type can be nil or minOccurs set to '0'*
*</message>*
<portType name="pt1">
<operation name="GetCompanyInfo">
<input message="m1"/>
*<output message="m2"/> -----> multi part message.*
</operation>
</portType>
Now here is sample message for the request(I've composed this message for this question):
<soap:Envelope> MESSAGE1
<soap:header/>
<soap:body>
<tns:m2>
<tns:GetCompanyInfoResult>
Blah Blah....
</tns:GetCompanyInfoResult>
<tns:docs>
Blah Blah....
</tns:docs> Assume no data for 'logo', so it's not returned. Since all its elements can be nillable.
<tns:m2>
</soap:body>
</soap:Envelope>
First of all, is this SOAP response is valid? I'm not sure about *'message' and 'parts' in SOAP*, but according to XML schema standards it's invalid.
Because, according to *'message' m2, 'logo' is missing*, eventhough all it's elements are nillable in such case there should be *<logo/>* at the end.
I mean valid message should be like below
<soap:Envelope> '*MESSAGE2*'
<soap:header/>
<soap:body>
<tns:m2>
<tns:GetCompanyInfoResult>
Blah Blah....
</tns:GetCompanyInfoResult>
<tns:docs>
Blah Blah....
</tns:docs>
*<tns:logo/> ------------------> here is the change compared to above message. empty element.*
<tns:m2>
</soap:body>
</soap:Envelope>
Now the concerns are :
(1) Which is a valid response? Message1 or Message2
(2) If message1 is valid then why is weblogic throwing an exception 'null SOAP element', I suppose this is due to missing 'logo' element.
(To confirm this I've used tcpmonitor and found message1 as response but weblogic is still throwing 'null SOAP Element' exception,
which confirms it needs 'logo' as well, I suppose <logo/> at least). Is there any workaround for this in weblogic for multi-part messages?
(3) If message1 is invalid according to SOAP standards then You've answered my question. ---> I need to talk to the webservice provider in this case.....
Thanks in advance...

Message 1 is not Basic Profile 1.1 compliant. It is specified by BP1.1 in section 4.4.1(http://www.ws-i.org/Profiles/BasicProfile-1.1-2004-08-24.html#Bindings_and_Parts) that when a wsdl:part element is defined using the type attribute, the serialization of that part in a message is equivalent to an implicit (XML Schema) qualification of a minOccurs attribute with the value "1", a maxOccurs attribute with the value "1" and a nillable attribute with the value "false".

Error when trying to read the SOAP Response

Hai,
iam trying to access the web service of DUBAI international Airport
GetFlightSchedulebyDateRange at http://dca.gov.ae/WebServices/Flights
This is my program
package MyClient3;
import java.io.FileOutputStream;
import java.net.URL;
import java.util.Iterator;
import javax.xml.soap.MessageFactory;
import javax.xml.soap.MimeHeaders;
import javax.xml.soap.Name;
import javax.xml.soap.SOAPBody;
import javax.xml.soap.SOAPBodyElement;
import javax.xml.soap.SOAPConnection;
import javax.xml.soap.SOAPConnectionFactory;
import javax.xml.soap.SOAPElement;
import javax.xml.soap.SOAPEnvelope;
import javax.xml.soap.SOAPFactory;
import javax.xml.soap.SOAPFault;
import javax.xml.soap.SOAPHeader;
import javax.xml.soap.SOAPMessage;
import javax.xml.soap.SOAPPart;
public class Client3 {
public static void main(String arg[]){
try{
MessageFactory factory = MessageFactory.newInstance();
SOAPMessage message = factory.createMessage();
SOAPPart soapPart = message.getSOAPPart();
SOAPEnvelope envelope = soapPart.getEnvelope();
SOAPHeader header = envelope.getHeader();
SOAPBody body = envelope.getBody();
// header.detachNode();
SOAPFactory soapFactory = SOAPFactory.newInstance();
Name bodyName = soapFactory.createName("GetFlightSchedulebyDateRange",null,"http://dca.gov.ae/WebServices/Flights");
SOAPBodyElement bodyElement = body.addBodyElement(bodyName);
Name name = soapFactory.createName("Todate");
SOAPElement symbol = bodyElement.addChildElement(name);
//symbol.addTextNode("2007-05-25T00:00:00.0000000+04:00");
symbol.addTextNode("2007-05-27");
name = soapFactory.createName("Fromdate");
symbol = bodyElement.addChildElement(name);
//symbol.addTextNode("2007-05-25T00:00:00.0000000+04:00");
symbol.addTextNode("2007-05-27");
MimeHeaders hd = message.getMimeHeaders();
hd.addHeader("SOAPAction", "http://dca.gov.ae/WebServices/Flights/GetFlightSchedulebyDateRange");
SOAPConnectionFactory soapConnectionFactory = SOAPConnectionFactory.newInstance();
SOAPConnection connection = soapConnectionFactory.createConnection();
message.writeTo(System.out);
System.out.println();
System.out.println(soapPart.toString());
String endpoint = "http://dubaiairport.com/dcaflightinfo/fis/flights.asmx?WSDL";
URL url = new URL(endpoint);
SOAPMessage response = connection.call(message, url);
response.writeTo(System.out);
SOAPPart part = response.getSOAPPart();
SOAPEnvelope env = part.getEnvelope();
connection.close();
System.out.println("\n\nIterating through the response object to get the values:\n\n");
// SOAPBody se = response.getSOAPBody();
}catch(Exception e){System.out.println("+++++++++++++++++++++++++"+e);}
i am getting the error
ERROR: 'Character reference "&#x1B" is an invalid XML character.
in the statement
SOAPEnvelope env = part.getEnvelope();
can some help me to solve this problem, iam using JAX-WS 2.0, and netbeans

I got the solution, there was a Invalid char in SOAP response message, i stored the SOAP res msg to a file, parsed that file to remove the invalid char , ans used the soap msg from the file,
it worked perfectly fo me

SOAP Response From ASP Page gives Exceptions-Why ?

Hi Friends,
I am trying to call an ASP Page by sending it a SOAP Request.
The SOAP Request reaches the ASP Page but still i am getting lot of
exceptions.This is my code from Request.java
import javax.xml.soap.*;
import java.util.*;
import java.net.URL;
public class Request {
public static void main(String[] args) {
try {
SOAPConnectionFactory scFactory =
SOAPConnectionFactory.newInstance();
SOAPConnection con = scFactory.createConnection();
MessageFactory factory =
MessageFactory.newInstance();
SOAPMessage message = factory.createMessage();
SOAPPart soapPart = message.getSOAPPart();
SOAPEnvelope envelope = soapPart.getEnvelope();
SOAPHeader header = envelope.getHeader();
SOAPBody body = envelope.getBody();
header.detachNode();
Name bodyName = envelope.createName(
"TestDtls", "m",
"urn:myserver/soap:TestThis");
SOAPBodyElement gltp =
body.addBodyElement(bodyName);
Name name = envelope.createName("PhoneOrigin");
SOAPElement symbol = gltp.addChildElement(name);
symbol.addTextNode("0672324228");
URL endpoint = new URL
("http://john/myservices/testsoap.asp");
 message.writeTo(System.out);
SOAPMessage response = con.call(message, endpoint);
 response.writeTo(System.out);
SOAPPart sp = response.getSOAPPart();
SOAPEnvelope se = sp.getEnvelope();
SOAPBody sb = se.getBody();
Iterator it = sb.getChildElements(bodyName);
SOAPBodyElement bodyElement =
(SOAPBodyElement)it.next();
String myvalue = bodyElement.getValue();
System.out.print("The Value Retrived is ");
System.out.println(myvalue);
 con.close();
} catch (Exception ex) {
 System.out.println(ex);
This is what i have in my ASP Page: testsoap.asp
<%
Set objReq = Server.CreateObject("Microsoft.XMLDOM")
objReq.load(Request)
strmycode = "SOAP-ENV:Envelope/SOAP-ENV:Body/m:TestDtls/PhoneOrigin"
varPhoneOrigin=objReq.SelectSingleNode(strmycode).text
status="ok"
strReturn = "<SOAP-ENV:Envelope xmlns:SOAP=""urn:schemas-xmlsoap-org:soap.v1"">" & _
"<SOAP-ENV:Header></SOAP-ENV:Header>" & _
 "<SOAP-ENV:Body>" & _
 "<m:TestDtlsResponse xmlns:m=""urn:myserver/soap:TestThis"">" & _
 "<PhoneStatus>" & Status & "</PhoneStatus>" & _
 "</m:TestDtlsResponse>" & _
 "</SOAP-ENV:Body>" & _
 "</SOAP-ENV:Envelope>"
Response.Write strReturn
%>
The Exceptions i get are as follows:
=====================================
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"><S
OAP-ENV:Body><m:TestDtls xmlns:m="urn:myserver/soap:TestThis"><PhoneOrigin>"0672
324228"</PhoneOrigin></m:TestDtls></SOAP-ENV:Body></SOAP-ENV:Envelope>Jul 11, 20
03 6:37:35 PM com.sun.xml.messaging.saaj.soap.MessageImpl identifyContentType
SEVERE: SAAJ0537: Invalid Content-Type. Could be an error message instead of a S
OAP message
com.sun.xml.messaging.saaj.SOAPExceptionImpl: Invalid Content-Type:text/html. Is
this an error message instead of a SOAP response?
at com.sun.xml.messaging.saaj.soap.MessageImpl.identifyContentType(Messa
geImpl.java:268)
at com.sun.xml.messaging.saaj.soap.MessageImpl.<init>(MessageImpl.java:1
35)
at com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl.<init>(Message1
_1Impl.java:45)
at com.sun.xml.messaging.saaj.soap.ver1_1.SOAPMessageFactory1_1Impl.crea
teMessage(SOAPMessageFactory1_1Impl.java:32)
at com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.post(HttpSOA
PConnection.java:361)
at com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection$PriviledgedP
ost.run(HttpSOAPConnection.java:156)
at java.security.AccessController.doPrivileged(Native Method)
at com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.call(HttpSOA
PConnection.java:126)
at Request.main(Request.java:34)
Jul 11, 2003 6:37:35 PM com.sun.xml.messaging.saaj.soap.MessageImpl <init>
SEVERE: SAAJ0535: Unable to internalize message
com.sun.xml.messaging.saaj.SOAPExceptionImpl: Unable to internalize message
at com.sun.xml.messaging.saaj.soap.MessageImpl.<init>(MessageImpl.java:2
02)
at com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl.<init>(Message1
_1Impl.java:45)
at com.sun.xml.messaging.saaj.soap.ver1_1.SOAPMessageFactory1_1Impl.crea
teMessage(SOAPMessageFactory1_1Impl.java:32)
at com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.post(HttpSOA
PConnection.java:361)
at com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection$PriviledgedP
ost.run(HttpSOAPConnection.java:156)
at java.security.AccessController.doPrivileged(Native Method)
at com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.call(HttpSOA
PConnection.java:126)
at Request.main(Request.java:34)
Caused by: com.sun.xml.messaging.saaj.SOAPExceptionImpl: Invalid Content-Type:te
xt/html. Is this an error message instead of a SOAP response?
at com.sun.xml.messaging.saaj.soap.MessageImpl.identifyContentType(Messa
geImpl.java:268)
at com.sun.xml.messaging.saaj.soap.MessageImpl.<init>(MessageImpl.java:1
35)
... 7 more
CAUSE:
com.sun.xml.messaging.saaj.SOAPExceptionImpl: Invalid Content-Type:text/html. Is
this an error message instead of a SOAP response?
at com.sun.xml.messaging.saaj.soap.MessageImpl.identifyContentType(Messa
geImpl.java:268)
at com.sun.xml.messaging.saaj.soap.MessageImpl.<init>(MessageImpl.java:1
35)
at com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl.<init>(Message1
_1Impl.java:45)
at com.sun.xml.messaging.saaj.soap.ver1_1.SOAPMessageFactory1_1Impl.crea
teMessage(SOAPMessageFactory1_1Impl.java:32)
at com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.post(HttpSOA
PConnection.java:361)
at com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection$PriviledgedP
ost.run(HttpSOAPConnection.java:156)
at java.security.AccessController.doPrivileged(Native Method)
at com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.call(HttpSOA
PConnection.java:126)
at Request.main(Request.java:34)
CAUSE:
com.sun.xml.messaging.saaj.SOAPExceptionImpl: Invalid Content-Type:text/html. Is
this an error message instead of a SOAP response?
at com.sun.xml.messaging.saaj.soap.MessageImpl.identifyContentType(Messa
geImpl.java:268)
at com.sun.xml.messaging.saaj.soap.MessageImpl.<init>(MessageImpl.java:1
35)
at com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl.<init>(Message1
_1Impl.java:45)
at com.sun.xml.messaging.saaj.soap.ver1_1.SOAPMessageFactory1_1Impl.crea
teMessage(SOAPMessageFactory1_1Impl.java:32)
at com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.post(HttpSOA
PConnection.java:361)
at com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection$PriviledgedP
ost.run(HttpSOAPConnection.java:156)
at java.security.AccessController.doPrivileged(Native Method)
at com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.call(HttpSOA
PConnection.java:126)
at Request.main(Request.java:34)
java.security.PrivilegedActionException: com.sun.xml.messaging.saaj.SOAPExceptio
nImpl: Unable to internalize message
at java.security.AccessController.doPrivileged(Native Method)
at com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.call(HttpSOA
PConnection.java:126)
at Request.main(Request.java:34)
Caused by: com.sun.xml.messaging.saaj.SOAPExceptionImpl: Unable to internalize m
essage
at com.sun.xml.messaging.saaj.soap.MessageImpl.<init>(MessageImpl.java:2
02)
at com.sun.xml.messaging.saaj.soap.ver1_1.Message1_1Impl.<init>(Message1
_1Impl.java:45)
at com.sun.xml.messaging.saaj.soap.ver1_1.SOAPMessageFactory1_1Impl.crea
teMessage(SOAPMessageFactory1_1Impl.java:32)
at com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection.post(HttpSOA
PConnection.java:361)
at com.sun.xml.messaging.saaj.client.p2p.HttpSOAPConnection$PriviledgedP
ost.run(HttpSOAPConnection.java:156)
... 3 more
Caused by: com.sun.xml.messaging.saaj.SOAPExceptionImpl: Invalid Content-Type:te
xt/html. Is this an error message instead of a SOAP response?
at com.sun.xml.messaging.saaj.soap.MessageImpl.identifyContentType(Messa
geImpl.java:268)
at com.sun.xml.messaging.saaj.soap.MessageImpl.<init>(MessageImpl.java:1
35)
... 7 more
Actually,i need to see the response in XML format as per my program.
But,What does all this stuff mean ? I have using latest jwsdp 1.2.
Can Anyone Help me on this ?

i have the same problem. when i make a test with a VB client, the SOAP message is builded this way "<SOAP.... instead of <SOAP-ENV.... tag generated by java. When a make a test in vb client using this syntax (SOAP-ENV), the asp page returns a error:

Microsoft VBScript runtime error '800a01a8'

Object required: 'objXMLDOM.selectSingleNode(...)'

/rcruz/soap/vbSoap/simplesoap.asp, line 6
Anyone have a idea???
Thanks

Error Reading Soap Response

Hi,
We are having a problem reading Soap Response:
Scenario: From XI/PI we are calling a webservice with Synchronous
message with WS-Security including Authentication, Signature, TimeStamp
and Encryption using SOAP Receiver Adapter. We are able to send the
request successfully and also the webServer is able to understand the
request and sending the response back. The problem is the PI is unable
to read the response and giving a below error:
com.sap.aii.af.ra.ms.api.DeliveryException: expecting end tag:
Transform, but found
InclusiveNamespaces at state 1
We tested successfully end-end with NON-Secured sites with out WS-
Security.
Please let me know if you have seen this error or any thoughts.
Thanks,
Laxman
This is the actual Request Message:
<?xml version="1.0" encoding="UTF-8" ?>
<ns0:getUser xmlns:ns0="http://csa -namespace:8090/ddsssaws/IdentityManagementService">
<string>XYZ123</string>
</ns0:getUser>
Also we extracted raw traffic using TCPMon:
Below is the raw-traffic of SOAP adapter (used TCPGateway to capture the traffic)
Request:
POST /edsssaws/IdentityManagement HTTP/1.0
Accept: /
Host: 999.97.19.45:9999
User-Agent: SAP-Messaging-com.sap.aii.messaging/1.0505
Content-ID: <soap-1f3af770018111ddc0d300144f2515b0Atsap.com>
Content-Disposition: attachment;filename="soap-1f3af770018111ddc0d300144f2515b0Atsap.com.xml"
Content-Type: text/xml; charset=utf-8
Content-Description: SOAP
Content-Length: 5530
SOAPACTION:
<SOAP:Envelope xmlns:SOAP='http://schemas.xmlsoap.org/soap/envelope/'><SOAP:Header><wsse:Security xmlns:wsse='http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd' SOAP:mustUnderstand='1'><wsse:BinarySecurityToken xmlns:wsu='http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd' wsu:Id='sap-9' ValueType='http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3' EncodingType='http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary'>MIIFFTCCBH6gAwIBAgIKZptrmQABAAALBTANBgkqhkiG9w0BAQUFADByMRMwEQYKCZImiZPyLGQBGRYDY29tMRMwEQYKCZImiZPyLGQBGRYDZWRzMRQwEgYKCZImiZPyLGQBGRYEY29ycDEUMBIGCgmSJomT8ixkARkWBGFtZXIxGjAYBgNVBAMTEUVEUyBFbnRlcnByaXNlQ0ExMB4XDTA4MDQwMTIxMjMyN1oXDTEwMDQwMTIxMjMyN1owIjELMAkGA1UEBhMCVVMxEzARBgNVBAMTCklUQVBJTlRERVYwgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBALjKvScjIEmp5Q1X3/gfR0WZO22KiEAOAx9kM0q3kpT/0dk2ZVit5YCBT4Zkt6Tttyh21xmnCcVgcRo0YOxXcXrLq25HRsSbxY3Zu37qq4tqExX5gQCtfR1pRjRrhQfDPmPGzFOrTzSjxJ5BH49p3KZcUhj7KpWQEakDBvJAgMBAAGjggMAMIIC/DAdBgNVHQ4EFgQUadHS0gj0CBQymaNnAlGJphSCB/YwHwYDVR0jBBgwFoAULNVTI/CtjM0k4MlzJLuQI4tVUy8wggEaBgNVHR8EggERMIIBDTCCAQmgggEFoIIBAYaBxWxkYXA6Ly8vQ049RURTJTIwRW50ZXJwcmlzZUNBMSgxKSxDTj11c3Bsc3NjYTAwMixDTj1DRFAsQ049UHVibGljJTIwS2V5JTIwU2VydmljZXMsQ049U2VydmljZXMsQ049Q29uZmlndXJhdGlvbixEQz1jb3JwLERDPWVkcyxEQz1jb20/Y2VydGlmaWNhdGVSZXZvY2F0aW9uTGlzdD9iYXNlP29iamVjdENsYXNzPWNSTERpc3RyaWJ1dGlvblBvaW50hjdodHRwOi8vd3d3LmVkcy5jb20vY3J0cmV2bHN0L0VEUyUyMEVudGVycHJpc2VDQTEoMSkuY3JsMIIBDwYIKwYBBQUHAQEEggEBMIHMIG2BggrBgEFBQcwAoaBqWxkYXA6Ly8vQ049RURTJTIwRW50ZXJwcmlzZUNBMSxDTj1BSUEsQ049UHVibGljJTIwS2V5JTIwU2VydmljZXMsQ049U2VydmljZXMsQ049Q29uZmlndXJhdGlvbixEQz1jb3JwLERDPWVkcyxEQz1jb20/Y0FDZXJ0aWZpY2F0ZT9iYXNlP29iamVjdENsYXNzPWNlcnRpZmljYXRpb25BdXRob3JpdHkwQwYIKwYBBQUHMAKGN2h0dHA6Ly93d3cuZWRzLmNvbS9jcnRyZXZsc3QvRURTJTIwRW50ZXJwcmlzZUNBMSgxKS5jcnQwDAYDVR0TAQH/BAIwADALBgNVHQ8EBAMCBLAwPAYJKwYBBAGCNxUHBC8wLQYlKwYBBAGCNxUIh4qV4WN/hPFkRuHwclug63SWS2GpOIihPT8LwIBZAIBBDATBgNVHSUEDDAKBggrBgEFBQcDATAbBgkrBgEEAYI3FQoEDjAMMAoGCCsGAQUFBwMBMA0GCSqGSIb3DQEBBQUAA4GBAGzyuh56APinQtmE9oWsT8NHcQqMASHZnN26RAofnxuIUH1VyBK2CGyiiDnCS0cDIGBl45sqOO8uRClE7CngeZEAV9JL5bhpUF6rywmFKvqe5FyqnrScczeaODV0g9sO4vUrwdGlReA5ncvtSN/u82MWDqtHAHBfpYQxZUrW</wsse:BinarySecurityToken><wsu:Timestamp xmlns:wsu='http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd' wsu:Id='wsu-targetID-1f10b320-0181-11dd-aebd-00144f2515b0'><wsu:Created ValueType='xsd:dateTime'>2008-04-03T13:23:17Z</wsu:Created><wsu:Expires ValueType='xsd:dateTime'>2008-04-03T13:25:17Z</wsu:Expires></wsu:Timestamp><xenc:EncryptedKey xmlns:xenc='http://www.w3.org/2001/04/xmlenc#' Id='EK52789332'><xenc:EncryptionMethod Algorithm='http://www.w3.org/2001/04/xmlenc#rsa-1_5'/><ds:KeyInfo xmlns:ds='http://www.w3.org/2000/09/xmldsig#'><wsse:SecurityTokenReference><wsse:KeyIdentifier ValueType='http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509SubjectKeyIdentifier' EncodingType='http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary'>ykCivrkfwQdj30aJid9VGnjtY=</wsse:KeyIdentifier></wsse:SecurityTokenReference></ds:KeyInfo><xenc:CipherData><xenc:CipherValue>Fi5B3uBMSp4nAKh3rLAs4DJQ5iCLoupE1oq3VOFueea1Y90xI200OFraV2mRS2ywsejH36nwy
XYPuB5ZQScJampqZDtTR28cq890s4sEKFpycsNyNM9VScWaVoi4nKBKRIdGVoLgLf+NrmzJnXD
6eb4F6tWWyw8g2FJel4=</xenc:CipherValue></xenc:CipherData><xenc:ReferenceList><xenc:DataReference URI='#ED13608949'/></xenc:ReferenceList></xenc:EncryptedKey><ds:Signature xmlns:ds='http://www.w3.org/2000/09/xmldsig#'><ds:SignedInfo><ds:CanonicalizationMethod Algorithm='http://www.w3.org/2001/10/xml-exc-c14n#'/><ds:SignatureMethod Algorithm='http://www.w3.org/2000/09/xmldsig#rsa-sha1'/><ds:Reference URI='#wsuid-body-1f108c10-0181-11dd-838e-00144f2515b0'><ds:Transforms><ds:Transform Algorithm='http://www.w3.org/2001/10/xml-exc-c14n#'/></ds:Transforms><ds:DigestMethod Algorithm='http://www.w3.org/2000/09/xmldsig#sha1'/><ds:DigestValue>UaW58GCrg/nrA/EfW+OyHP2DCio=</ds:DigestValue></ds:Reference><ds:Reference URI='#wsu-targetID-1f10b320-0181-11dd-aebd-00144f2515b0'><ds:Transforms><ds:Transform Algorithm='http://www.w3.org/2001/10/xml-exc-c14n#'/></ds:Transforms><ds:DigestMethod Algorithm='http://www.w3.org/2000/09/xmldsig#sha1'/><ds:DigestValue>LFuszgJ412Fe8PRtK3W69RTXndY=</ds:DigestValue></ds:Reference></ds:SignedInfo><ds:SignatureValue>K4iZoVGhuI41fj9BdXx7wUz/JEi2pqh60gZZta8tOfaVmC1PfNtPg61N0sYescfM4RmkQpDorS1d
VB/DAJKz173HTD5rn/SuwmYgql4aVKPNlIDD90ZXoJ/mfzwT/Kei6yjWtvCYthCxaUtP/LFDB/dA
mr1OUAj9X2DHkzF6g=</ds:SignatureValue><ds:KeyInfo><wsse:SecurityTokenReference><wsse:Reference URI='#sap-9'/></wsse:SecurityTokenReference></ds:KeyInfo></ds:Signature></wsse:Security></SOAP:Header><SOAP:Body xmlns:wsu='http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd' wsu:Id='wsuid-body-1f108c10-0181-11dd-838e-00144f2515b0'><xenc:EncryptedData xmlns:xenc='http://www.w3.org/2001/04/xmlenc#' Type='http://www.w3.org/2001/04/xmlenc#Content' Id='ED13608949'><xenc:EncryptionMethod Algorithm='http://www.w3.org/2001/04/xmlenc#tripledes-cbc'/><xenc:CipherData><xenc:CipherValue>lZkC7zZZfqBUg5rnqMZypi5ZvnPBvw36fjeFmCDQ5DMDjKXShO4apBjBE3gUsLGL1TMli18D0NWK
dmVHQTePitGhvQ7YiyaXgjekZckS2P91Qv/9Zut5/hzCYhgVarnUgGmr8Qi4aSYXCY0oBD6SzVXy
/UoQHPASF3mhYPaFBtmTJu2dHmV6v4HTKC+Om0</xenc:CipherValue></xenc:CipherData></xenc:EncryptedData></SOAP:Body></SOAP:Envelope>
Response:
HTTP/1.1 200 OK
Date: Thu, 03 Apr 2008 13:23:54 GMT
Content-Length: 9511
Content-Type: text/xml
Set-Cookie: JSESSIONID=cTPmH0hKYvKqK427JJb573FT1RWZhHY5l7XnLlsjsk6yRkS2g5y6!1973031667; path=/
Connection: close
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsd="http://www.w3.org/2001/XMLSchema"><env:Header><wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" env:mustUnderstand="1"><xenc:EncryptedKey xmlns:xenc="http://www.w3.org/2001/04/xmlenc#"><xenc:EncryptionMethod Algorithm="http://www.w3.org/2001/04/xmlenc#rsa-1_5"></xenc:EncryptionMethod><dsig:KeyInfo xmlns:dsig="http://www.w3.org/2000/09/xmldsig#"><wsse:SecurityTokenReference><wsse:KeyIdentifier xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509SubjectKeyIdentifier" wsu:Id="Id-dgdMMmsGkjae8aSYF_59_xwe" EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary">adHS0gj0CBQymaNnAlGJphSCB/Y=</wsse:KeyIdentifier></wsse:SecurityTokenReference></dsig:KeyInfo><xenc:CipherData><xenc:CipherValue>mbOmTXSiYuEiWHbP3dbrDXFpZaSoQ084wMBt7uRxNo49p1fpQBkDpr/H2wPNbHy4qzSTVzP7EESzWFjFEb/7BH3dt4JuyzBFH1M0X77YBW5YHNGpiUmj934ziydojqcU6jWBsUaFxXsAPmvy0q3vVk8xnZcQHxMNhPS5ebK9o=</xenc:CipherValue></xenc:CipherData><xenc:ReferenceList><xenc:DataReference URI="#Id-yMgwZrtQctSvW1mT1sDWdZ8D"></xenc:DataReference></xenc:ReferenceList></xenc:EncryptedKey><wsse:BinarySecurityToken xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3" wsu:Id="Id-2DXBQHwdRE0oquWQV0mjtw1U" EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary">MIIFVjCCBLgAwIBAgIKfps5MgABAAADHjANBgkqhkiG9w0BAQUFADByMRMwEQYKCZImiZPyLGQBGRYDY29tMRMwEQYKCZImiZPyLGQBGRYDZWRzMRQwEgYKCZImiZPyLGQBGRYEY29ycDEUMBIGCgmSJomT8ixkARkWBGFtZXIxGjAYBgNVBAMTEUVEUyBFbnRlcnByaXNlQ0ExMB4XDTA2MDUyMzIzMDY0OVoXDTA4MDUyMjIzMDY0OVowYzELMAkGA1UEBhMCVVMxCzAJBgNVBAgTAlRYMQ4wDAYDVQQHEwVQbGFubzEMMAoGA1UEChMDRURTMQwwCgYDVQQLEwNTRFMxGzAZBgNVBAMTElNTQVdlYlNlcnZpY2VzLURFVjCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEA0qRmvQkxnPnEZQNSabPVwM6sEf8vFUOAlgQ9uuiDImVmDw4Afg45zbmTBeDdv4wsIap7kI4VJhv60SdOQg6i1mIEi83Qk7UJYD8XvKuOalSLYhHu92lsp0kIZlAdzipVd1Pp0cI3wSvP6o9zfX0gALpisf8rGJ1CkVWbtHaVp0CAwEAAaOCAwAwggL8MB0GA1UdDgQWBBTKT4KKuR/7BB2PfRomJ31UaeO1jAfBgNVHSMEGDAWgBQs1VMj8K2MzSTgyXMku5Aji1VTLzCCARoGA1UdHwSCAREwggENMIIBCaCCAQWgggEBhoHFbGRhcDovLy9DTj1FRFMlMjBFbnRlcnByaXNlQ0ExKDEpLENOPXVzcGxzc2NhMDAyLENOPUNEUCxDTj1QdWJsaWMlMjBLZXklMjBTZXJ2aWNlcyxDTj1TZXJ2aWNlcyxDTj1Db25maWd1cmF0aW9uLERDPWNvcnAsREM9ZWRzLERDPWNvbT9jZXJ0aWZpY2F0ZVJldm9jYXRpb25MaXN0P2Jhc2U/b2JqZWN0Q2xhc3M9Y1JMRGlzdHJpYnV0aW9uUG9pbnSGN2h0dHA6Ly93d3cuZWRzLmNvbS9jcnRyZXZsc3QvRURTJTIwRW50ZXJwcmlzZUNBMSgxKS5jcmwwggEPBggrBgEFBQcBAQSCAQEwgf4wgbYGCCsGAQUFBzAChoGpbGRhcDovLy9DTj1FRFMlMjBFbnRlcnByaXNlQ0ExLENOPUFJQSxDTj1QdWJsaWMlMjBLZXklMjBTZXJ2aWNlcyxDTj1TZXJ2aWNlcyxDTj1Db25maWd1cmF0aW9uLERDPWNvcnAsREM9ZWRzLERDPWNvbT9jQUNlcnRpZmljYXRlP2Jhc2U/b2JqZWN0Q2xhc3M9Y2VydGlmaWNhdGlvbkF1dGhvcml0eTBDBggrBgEFBQcwAoY3aHR0cDovL3d3dy5lZHMuY29tL2NydHJldmxzdC9FRFMlMjBFbnRlcnByaXNlQ0ExKDEpLmNydDAMBgNVHRMBAf8EAjAAMAsGA1UdDwQEAwIEsDA8BgkrBgEEAYI3FQcELzAtBiUrBgEEAYI3FQiHir5XhY3E8WRG4fByW6DrdJZLYak4iKE9PwvAgFkAgEEMBMGA1UdJQQMMAoGCCsGAQUFBwMBMBsGCSsGAQQBgjcVCgQOMAwwCgYIKwYBBQUHAwEwDQYJKoZIhvcNAQEFBQADgYEALsVozc1aVcPNBVsRXRbAiStchxG2fKDOt9kRzL6BHtQa/fkp81EjOBhETn8N1IHLUsINn05wGgdDA2UszjLtRIpQmdpCyh2gzFW8Dlx5X7vJyvJsoDOPDBArv55dTjCEfok1oz3ux3mrVotuvr1pKIVTr7ylpRM8p8GBXw=</wsse:BinarySecurityToken><dsig:Signature xmlns:dsig="http://www.w3.org/2000/09/xmldsig#"><dsig:SignedInfo><dsig:CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"></dsig:CanonicalizationMethod><dsig:SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1"></dsig:SignatureMethod><dsig:Reference URI="#Id-wS1xP_ArcYYXY4qkqYznI7_W"><dsig:Transforms><dsig:Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"></dsig:Transform></dsig:Transforms><dsig:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"></dsig:DigestMethod><dsig:DigestValue>tr3NrozQWsKrvH38naIEnQXrzgQ=</dsig:DigestValue></dsig:Reference><dsig:Reference URI="#Id-1vPAqVSMhSLH3WiBQkTTfldz"><dsig:Transforms><dsig:Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"><c14n:InclusiveNamespaces xmlns:c14n="http://www.w3.org/2001/10/xml-exc-c14n#" PrefixList="xsd n1"></c14n:InclusiveNamespaces></dsig:Transform></dsig:Transforms><dsig:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"></dsig:DigestMethod><dsig:DigestValue>AUWlqeyq6w5LQnggK5dT6flLUU=</dsig:DigestValue></dsig:Reference></dsig:SignedInfo><dsig:SignatureValue>Yx5Pre8VChTLOhPVln5xhO21dM93a2FPxQTsZY1BBIWlqeHkAEQqXvhI/EU459QZIGDOubLK0Z9AT0SRmDOgtnWNBT0duqveQ1Ippbd0hXaehW48ObrMIKnYfq5ub1kNYv9mslybPRZw9OaiijNmLfIty8qc8ctRV0lFwAjcQyk=</dsig:SignatureValue><dsig:KeyInfo><wsse:SecurityTokenReference><wsse:Reference URI="#Id-2DXBQHwdRE0oquWQV0mjtw1U"></wsse:Reference></wsse:SecurityTokenReference></dsig:KeyInfo></dsig:Signature><wsu:Timestamp xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="Id-wS1xP_ArcYYXY4qkqYznI7_W"><wsu:Created>2008-04-03T13:23:55.459Z</wsu:Created></wsu:Timestamp></wsse:Security></env:Header><env:Body xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" wsu:Id="Id-1vPAqVSMhSLH3WiBQkTTfldz"><xenc:EncryptedData xmlns:xenc="http://www.w3.org/2001/04/xmlenc#" Type="http://www.w3.org/2001/04/xmlenc#Content" Id="Id-yMgwZrtQctSvW1mT1sDWdZ8D"><xenc:EncryptionMethod Algorithm="http://www.w3.org/2001/04/xmlenc#tripledes-cbc"></xenc:EncryptionMethod><xenc:CipherData><xenc:CipherValue>LB6IKwEJgvTPdPGNeIzcpjPjC9GXi3sou5PaCnF3m4x6ToA6gDV5Sw/ODnCEeqFURgWFX8ZgxYF9YJdyj7ERAifs8MNBh/rHCitT02mU8pirwGdqSXlfCX4KYsHtUnyiGKbbMCwvCCs4LgBPnx8tCN39aazA1Ge/5JPfwupYMU/lAbyajdP1qva/gxhMCqGkgAnQgB1TJDfARvDsJnx6p2zqKsnRnNreBFClyBG7GHeMvpnzg4poPCFlj2baIoK2CSQmVbPdcPk4rgg1PAWDQwIIzBCKpZjysHeb/sW9jObekbnn4mCnUdzjRERoklstpZNeWKi/jLEaNsIX1ixhsUyWIyknYGaBjDiiGqmS6BIO1RHu0SydiMv1L/FzIWgyO9VhilGdTWsVDP6CxljxTqg41bobuPazkjQHyBK9rCGQI9J/bjSiA2S6FBDHxhA6SfDjyhvGzDhGNLMd/***2ieUGQWg/atFbqItqW2HZzb7T0cuIiROBYaGLUbWnghcUXAn9dV38GbCMfWk65OhpkD5EQXr/5bPxK41L3sPIrAs2JnMM9nLuj6gLo35VMlsdVQ1c0o3JYQ4JARnSlnUrgW20Cilwf3Fn2m7Yj4QicC6RUhChEudnbgYIjqq0Ypc8BsjJWAPYRuVAUVArINqgUjCNuOxQKV3dyEayS0lZ8UOBfopGBnIlEDS9h62ZIiIKfRhCD6xLsY1PED7K5ZHRvj2TEtQtYoZxeTNDH7/IdukO/cATF9B0DhSvx2YK8EzlG3pygcLGeHZ4DfwmGC5lnO5NZrqFaHXa1LNNgZ9H1rezZyOfizbvT/O5mC8tvINNvP5Ik37OdD6Lmjnc4u0gAKee6QqQ7uk8A6xbrjrnOWp46vnoNmvMZxyAMAD8xFBz9b8MVHu0IJX5etLdRbjsSsMYNpUomqFjfweFe3NeHESUA5IhkYUQVNNwJJ3MCpJDWWHFNLEbzRoUolXVOQhC0PC6j6KmHQH2yib0KWKKJn7kLrUtgGazJMatLDhWDU5oEtZbDJzauxikxto0R6ZirhjKqmVCeVu51yrbW4lgC2upXxJsQ2q5igBaX7Qvz4D1ICkp1m7CRG7cWrU6MfBSXusRsPIp/7wJsdBpXSPb97cZi6y82EP6iQhsyRJ9YODUr22WObb4CvIYo8bDFW1Sw6BImoqkgsoXB/j2oNp0g6vLhYy0OjF5LAdDbhDk23WA00KGj9xAHEPVkqfXdivfc3quxWdpIBri0JnQGA/T1GsxwM4YKvhp5hPl28sgLeo7/I0DstkK6Jispkt5/03N364bRQBAHykAqUAyDvMHz8jiZK0Jo2cnTDTzoDtDi9q2wbSI25lh31FZ68kKJ1t399VRdF4JlSKvaXE8pj1ljE3J6GsII6haD3W17Kns2hmnduL0pEeChUgq0VrXaK8k5e0CR1JdmzVEHNo7WKWwB901cOrtRfxh1yQWvw0dHCSlxzAlISAb7Y2t0MlIoITIKi9XzJSpbxtp5zCQiup3PPDni1wQWotYd9WVZ2Zs2KxDkusDbENOAu68RjtWoOQxGXPrek73CQ9ja2D6doNjdbwX9Exrhqlek9507Sn0J2RO5kJG6huXD3TTXcBcBlD8HYq76JfSNtqgpUwKztPCxaECMmvTm4n1YRT5pkpKfOmlx262TJllv1l2B5cs3f6ODWf/ULarjwMPT2ajviYvCDXl4Kl8HNcmXKhR3W8IzCvWCsPwwDoFbjCk5Xkdd6IVPAX9i0LP5hZqS1bMrJnTreNTVd4glne7T6SdjkFt2MR1UJnsNHlVDoeGhb5VhfphgPg2r1DUyY7k3QlXHGxCBctjlkTUVg9D0NgWf4JrE2KXtdCPR/gX7HjrR6wq24UsibqOH5yi2Zh2hGwP2OWrPRQ6QMqIdW2voAux0GOkL7Ip8GCRml5eilopmRyh8D3PxWw8CwfC81slylodVHvGP8AjGE9cddQhMzQ2s96ZPQVTLEo734UQFkH511HtJGWVCTbxGBmtpEyoJZSJJ9CeG2sXuwEGF7YXR31xJJZbtOKFyskQw3BJGb1SE35iF5lr0hshYB1/gm2YmlTX68nZtux9NWRIKnJ3EHvWUc9UIudzoEMf0LyLZm5pFtkZAUQ16F4BfqEVJekVlUBOs1dCSYN6lUcsVzinhUcY1eBni75vEXaO8zSTy4ZwcOiGYvR9QK2bSuzYen1LKBaFK6UIAVstr29avGAGp5nk3qM63/05rUv2jnDM6XYIoFSx1lpE7SwtvbiRUQjgUA4ZX7Oa7Mp9HJj5W0o7ZVViKbYTtxux5/2AXgXxLo/i3YsHd7BUE/2KTjUrKokTYUzCgTlXkSmYOfRY1wdxeixrLfbSWBD1Y4ZbcMw3l/57XIPmGl42HrRyEFIxGnt7kQHR9A3abfJ93E0Y8AMiQuhG2/WTZho/IzxQ/OfDJm78o97K10pbe7OUIrfpPNTfM3cenEd37ZFWI67yPNwYfiZw8E7uks8GIKSAqrt7q55C10EpmizEcydD5EKtGyElXk6ifr3GO6WbHJNUp6FvgyHQTF6VXRiC91Rv/ZvUQggxRDyF6HibOq5BqDwTbMY0OnbB6nR3KlGYfhkBfEUiqbd10HYzCzWx0uGv54swAwsRUtOQFMpbr5B17yXdE5vGN2uTm02Bgr3EwOUyuw2ttgdUedDH8APmOlDr23wPiFljsTgWbbX/UZQGCyhNxa8avQtDdlymu8e8PS5tMupjMSkJtULUUXQyoKGwcXwwvp25iubNODEt5aZNt45bGKwOW5P3Xzu2ZJ6tAtW/zh7NfN1EHVZIwIlxWgPaag0ComeirsmZfNu3W2wge7Cg9aOYws81iIRaLa0YgYWZwH3C6yTRRQcM8fx1U1TiK2tIkFcc4iAjefZKMHBsodtTzo4EYaYvb9SyjGgZLTMYSlTbpx31Ot0T/t8kFxpML/ObDgoKoxWUVXxfD74HDW/0Uo9JDgdaV/lxJ2CJ7y8gb4ayKsVRNB4BmP5OzA/q9vzZWgtfoM4ODu//vsAed9Dvi4f1pJt5Cf8WWxv1PtWS4gvFe87a03kyhwSzI4obai23oYlCcyrUyL9LBZCwcBgn4tDcno6HPIHT2iEpi00sTuTD2bqXyTkXrxgzGSwlfBzCXr7xczoZDJoU5oj5t59cyq/faUZZkhc0bb8dhOH2/oYcanpfdtNS64VeO42eXaPbkMP00IrHTAUb2KxXQa7h80vB3LMA29cS3EBaJ8pnIJ/sPh0bT5A/FiiiJVJNm8g7EBcvd2nbJWRAkVNp1SxLPoUKF1dRt3OiJwhbdOASOnmJS8IXRjskuIYRsMgXSNdlMGxadedsdB9TKRvgzGkutWu9mQ3+0XJJIp7S23E8b3OLH1CAxhH3wyWu8TmeksImbGc0VY7oSTTtNNWOdeRDQ==</xenc:CipherValue></xenc:CipherData></xenc:EncryptedData></env:Body></env:Envelope>

Any thoughts???
Appreciate your input.
Thanks,
Laxman

XML in SOAP response

Hi,
I wrote my own SOAP web service and so far it is working like a charm. I am trying now to use it in my own iPhone app but I keep getting the SOAP response as HTML entities (< become <) and I can not parse the XML like that.
I think the reason for this is that I specified on the SOAP WSDL that the response will be an string:
<part name='Result' type='xsd:string'/>
I can still modify my SOAP if I have to. What type of response should I use to avoid the HTML entities on my response?
Thank you.

Hi,
Thank you for your response.
The SOAP response headers are coming back in their proper XML format, but I am expecting an string that is an XML list (beside the SOAP headers) and that is what is being converted.
My suspicion is that I should declare a simple type just for XML and not treat it like an string. Your thoughts?
<SOAP-ENV:Body>
<ns1:getPartsResponse>
<Result xsi:type="xsd:string">
<catalog>
<result id="1">
<part>AAAAAAAAAAA</part>
<qty>0000000000</qty>
<mfg>XXXXXXXXXXXXX</mfg>
</result>
</catalog>
</Result>
</ns1:getPartsResponse>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>

Wsdl - soap response...

I am working on java ,using Eclipse wit wtp and Apache Axis. The soap request is sent, an xml file is parsed and I want to generate soap responses from the xml file.
Now i can send a soap request, parse the xml, but the response am getting is not of soap format, its jus a simple data...
For eg.. if the request is add no.s ( 5+ 7) i get the sum(12) or if i request for author of a book from i just get author's name..
Instead i want it as a soap response... some thing like this for requesting the stock price...
<?xml version="1.0"?>
<soap:Envelope
xmlns:soap="http://www.w3.org/2001/12/soap-envelope"
soap:encodingStyle="http://www.w3.org/2001/12/soap-encoding">
<soap:Body xmlns:m="http://www.example.org/stock">
 <m:GetStockPriceResponse>
 <m:Price>34.5</m:Price>
 </m:GetStockPriceResponse>
</soap:Body>
</soap:Envelope>
How do i get the sopa response using the wsdl file that gets generated... ????
Or is there another way of generating the soap responses.. ?
Plz help me out...

Hi,
All that you want to do is trying to call a web service and get the response from it, you can use the WSDLs from any weather or lets say google. From XI you can call it and you would get response in SOAP format.
If you want to create a web service, create a SOAP to RFC scenario in XI where RFC returns you some thing that you wanted in sync fashion. Now use the WSDL genrated from this scenario and import in XI for another scenario.. where it could be a HTTP to SOAP. Now you would get the response of RFC in SOAP format it self..
VJ

SOAP Response Unmarshal Problem

I am using the SOAP Proxy Generator to generate stubs from a WSDL file. This part is okay.
When I use a method in the stub, the runtime generates an exception -- "null". Yes that all it says. I have verified that there is a SOAP response. You can find the actual response text below.
I have traced the problem to the following statement in the generated stub:
perm.unmarshal((SOAPElementImpl) result, container);
Does anyone know if this SOAP response is something that the SOAP client SDK can support?
<?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" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" soap:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns5="http://www.themindelectric.com/package/com.esri.is.services.glue.v2.mapimage/" xmlns:ns6="http://www.themindelectric.com/package/com.esri.is.services.common.v2.geom/">
<soap:Body>
<n:getMapResponse xmlns:n="http://arcweb.esri.com/v2">
<Result href="#id0"/>
</n:getMapResponse>
<id0 id="id0" soapenc:root="0" xsi:type="ns5:MapImageInfo">
<mapUrl xsi:type="xsd:string">http://redlandsarcweb.esri.com/out/maps/GDT_ArcWeb_US_mangomap1735235894.jpg</mapUrl>
<legendUrl xsi:type="xsd:string">http://redlandsarcweb.esri.com/out/maps/GDT_ArcWeb_US_mangomap1735235895.jpg</legendUrl>
<mapExtent href="#id1"/></id0>
<id1 id="id1" soapenc:root="0" xsi:type="ns6:Envelope">
<minx xsi:type="xsd:double">-127.666666666666</minx>
<miny xsi:type="xsd:double">20.0000000000001</miny>
<maxx xsi:type="xsd:double">-106.333333333333</maxx>
<maxy xsi:type="xsd:double">35.9999999999999</maxy>
</id1>
</soap:Body>
</soap:Envelope>

I'm afraid the response I incuded earlier in this forum is a "touched" version. I got it by using the response object in the generated stub.
I spoke to the developers of the web service and the response should look like:
<n:getMapResponse xmlns:n='http://arcweb.esri.com/v2' xmlns:ns1='http://www.themindelectric.com/package/com.esri.is.services.glue.v2.mapimage/' xmlns:ns2='http://www.themindelectric.com/package/com.esri.is.services.common.v2.geom/'>
<Result id='id0' xsi:type='ns1:MapImageInfo'>
 <mapUrl
xsi:type='xsd:string'>http://redlandsarcweb.esri.com/out/maps/GDT_ArcWeb_US_
blackmap606135221.png
 </mapUrl>
 <legendUrl xsi:type='xsd:string'></legendUrl>
 <mapExtent id='id1' xsi:type='ns2:Envelope'>
 <minx xsi:type='xsd:double'>-117.256667</minx>
 <miny xsi:type='xsd:double'>33.980556</miny>
 <maxx xsi:type='xsd:double'>-117.106667</maxx>
 <maxy xsi:type='xsd:double'>34.1305559999999</maxy>
 </mapExtent>
</Result>
</n:getMapResponse>
Is there a way to get the "actual" SOAP response that was received direct from the web service? What is the official debugging method?

SOAP response customize body

Similar Messages

Maybe you are looking for