SOAP Response conatins no quots, no opening or closing tags.

Hello All,
I have developed WebService and I have deployed it on a server, and I have developed client that speak with the WebService via the JDeveloper generated EmbeddedIntegrationWebServiceStub and everything goes greatly when the WebService and the Client are running locally, also it works greatly when the WebService are hosted on server and the client run locally but after I deployed the client to another testing server I found strange behavioure that the returned soap repsonse to the client contans no < or > or "" so I make some dummy solution to regenerate the missing <, >, or "" but the server (hosting the client) keeps giving me the following exception
bq. 08/10/14 00:02:18 org.apache.xmlbeans.XmlException: error: Unexpected element: CDATA \\ 08/10/14 00:02:18 at org.apache.xmlbeans.impl.store.Locale$SaxLoader.load(Locale.java:3486) \\ 08/10/14 00:02:18 at org.apache.xmlbeans.impl.store.Locale.parse(Locale.java:712) \\ 08/10/14 00:02:18 at org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:696) \\ 08/10/14 00:02:18 at org.apache.xmlbeans.impl.store.Locale.parseToXmlObject(Locale.java:683) \\ 08/10/14 00:02:18 at org.apache.xmlbeans.impl.schema.SchemaTypeLoaderBase.parse(SchemaTypeLoaderBase.java:208) \\ 08/10/14 00:02:18 at ae.dxbpolice.eps.xml.xmlBeans.ProcVersionsDocument$Factory.parse(Unknown Source) \\ 08/10/14 00:02:18 at ae.dxbpolice.eps.tld.tag.FormCustomTag.doStartTag(FormCustomTag.java:158) \\ 08/10/14 00:02:18 at eps_integration._jspService(_eps__integration.java:65) \\ 08/10/14 00:02:18 at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:56) \\ 08/10/14 00:02:18 at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:347) \\ 08/10/14 00:02:18 at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:509) \\ 08/10/14 00:02:18 at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:413) \\ 08/10/14 00:02:18 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) \\ 08/10/14 00:02:18 at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:810) \\ 08/10/14 00:02:18 at com.evermind.server.http.ServletRequestDispatcher.include(ServletRequestDispatcher.java:121) \\ 08/10/14 00:02:18 at com.evermind.server.http.GetParametersRequestDispatcher.newInclude(GetParametersRequestDispatcher.java:80) \\ 08/10/14 00:02:18 at com.evermind.server.http.GetParametersRequestDispatcher.include(GetParametersRequestDispatcher.java:34) \\ 08/10/14 00:02:18 at com.evermind.server.http.EvermindPageContext.include(EvermindPageContext.java:267) \\ 08/10/14 00:02:18 at e_services._jspService(_e__services.java:333) \\ 08/10/14 00:02:18 at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:56) \\ 08/10/14 00:02:18 at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:347) \\ 08/10/14 00:02:18 at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:509) \\ 08/10/14 00:02:18 at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:413) \\ 08/10/14 00:02:18 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) \\ 08/10/14 00:02:18 at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:65) \\ 08/10/14 00:02:18 at ae.gov.dphq.internet.util.InternetFilter.doFilter(InternetFilter.java:111) \\ 08/10/14 00:02:18 at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:649) \\ 08/10/14 00:02:18 at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:322) \\ 08/10/14 00:02:18 at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:790) \\ 08/10/14 00:02:18 at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:208) \\ 08/10/14 00:02:18 at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:125) \\ 08/10/14 00:02:18 at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186) \\ 08/10/14 00:02:18 at java.lang.Thread.run(Thread.java:534) \\ 08/10/14 00:02:18 Caused by: org.xml.sax.SAXParseException: Unexpected element: CDATA \\ 08/10/14 00:02:18 at org.apache.xmlbeans.impl.piccolo.xml.Piccolo.reportFatalError(Piccolo.java:1038) \\ 08/10/14 00:02:18 at org.apache.xmlbeans.impl.piccolo.xml.Piccolo.parse(Piccolo.java:723) \\ 08/10/14 00:02:18 at org.apache.xmlbeans.impl.store.Locale$SaxLoader.load(Locale.java:3454) \\ 08/10/14 00:02:18 ... 32 more \\ 08/10/14 00:02:18 javax.servlet.jsp.JspTagException: SimpleTag: error: Unexpected element: CDATA \\ 08/10/14 00:02:18 at ae.dxbpolice.eps.tld.tag.FormCustomTag.doStartTag(FormCustomTag.java:277) \\ 08/10/14 00:02:18 at eps_integration._jspService(_eps__integration.java:65) \\ 08/10/14 00:02:18 at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:56) \\ 08/10/14 00:02:18 at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:347) \\ 08/10/14 00:02:18 at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:509) \\ 08/10/14 00:02:18 at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:413) \\ 08/10/14 00:02:18 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) \\ 08/10/14 00:02:18 at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:810) \\ 08/10/14 00:02:18 at com.evermind.server.http.ServletRequestDispatcher.include(ServletRequestDispatcher.java:121) \\ 08/10/14 00:02:18 at com.evermind.server.http.GetParametersRequestDispatcher.newInclude(GetParametersRequestDispatcher.java:80) \\ 08/10/14 00:02:18 at com.evermind.server.http.GetParametersRequestDispatcher.include(GetParametersRequestDispatcher.java:34) \\ 08/10/14 00:02:18 at com.evermind.server.http.EvermindPageContext.include(EvermindPageContext.java:267) \\ 08/10/14 00:02:18 at e_services._jspService(_e__services.java:333) \\ 08/10/14 00:02:18 at com.orionserver.http.OrionHttpJspPage.service(OrionHttpJspPage.java:56) \\ 08/10/14 00:02:18 at oracle.jsp.runtimev2.JspPageTable.service(JspPageTable.java:347) \\ 08/10/14 00:02:18 at oracle.jsp.runtimev2.JspServlet.internalService(JspServlet.java:509) \\ 08/10/14 00:02:18 at oracle.jsp.runtimev2.JspServlet.service(JspServlet.java:413) \\ 08/10/14 00:02:18 at javax.servlet.http.HttpServlet.service(HttpServlet.java:853) \\ 08/10/14 00:02:18 at com.evermind.server.http.ResourceFilterChain.doFilter(ResourceFilterChain.java:65) \\ 08/10/14 00:02:18 at ae.gov.dphq.internet.util.InternetFilter.doFilter(InternetFilter.java:111) \\ 08/10/14 00:02:18 at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:649) \\ 08/10/14 00:02:18 at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:322) \\ 08/10/14 00:02:18 at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:790) \\ 08/10/14 00:02:18 at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:208) \\ 08/10/14 00:02:18 at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:125) \\ 08/10/14 00:02:18 at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:186) \\ 08/10/14 00:02:18 at java.lang.Thread.run(Thread.java:534)
and this is the XML document that generate this problem
bq. <procVersions xmlns="http://www.xmlBeans.xml.eps.dxbpolice.ae"> \\ <procVersion id="2" beneficiaryType="EXTERNAL_PERSON" importanceLevel="NORMAL" isIncludeHierarchy="false" isNotifiable="false" isRemote="false" nameAR="ÇÌÑÇÁ æçÇêÉ ÇäÎÏåÉ" nameEN="Termination Procedure" status="ACTIVE" versionNo="V1"/> \\ <procVersion id="21" beneficiaryType="EXTERNAL_COMPANY" importanceLevel="NORMAL" isIncludeHierarchy="false" isNotifiable="false" isRemote="false" nameAR="ÇÌÑÇÁ ×äÈ ÃÌÇÒÉ" nameEN="Vacation Request Procedure" status="ACTIVE" versionNo="V2"/> \\ </procVersions>
so are there any suggestion about why the resposnse I got before my processing contains no < or > or " on the server however it comes gratly locally is there any library I should make sure that it doesn't exist on the server.
this is how the xml returned looks before manual adjustment
bq. procVersions xmlns=http://www.xmlBeans.xml.eps.dxbpolice.ae \\ procVersion id=2 beneficiaryType=EXTERNAL_PERSON importanceLevel=NORMAL isIncludeHierarchy=false isNotifiable=false isRemote=false nameAR=ÇÌÑÇÁ æçÇêÉ ÇäÎÏåÉ nameEN=Termination Procedure status=ACTIVE versionNo=V1/ \\ procVersion id=21 beneficiaryType=EXTERNAL_COMPANY importanceLevel=NORMAL isIncludeHierarchy=false isNotifiable=false isRemote=false nameAR=ÇÌÑÇÁ ×äÈ ÃÌÇÒÉ nameEN=Vacation Request Procedure status=ACTIVE versionNo=V2/ \\ /procVersions
and why it keeps giving me the same problem even after I have corrected the returned soap response manually
Thanks in advance
Edited by: Ali Abdel-Aziz on Oct 13, 2008 9:22 PM

ok, now my work arround works greatly as I was missing to pass the correct variable to the parser method and was passing the same old variable ;).
but I still wanna know what can be the reason for filtering the returned soap response and remove <, >, " from it.
Are there any Application Server configuration that can be the reason for this behavioure ?
thanks.
Edited by: Ali Abdel-Aziz on Oct 14, 2008 2:39 PM

Similar Messages

Matching opening and closing tags in MXML

Is possible to match the opening and closing tag in MXML with Flash Builder 4.x?
In AS3 you can see the curly braces highlighted and you can type Ctrl+Shift+P to jump from one bracket to the other.
In DreamWeaver you can see the hierarchy for every HTML element, and you can click any HTML element to highlight the block inside.
I can see only icons with - and + for contract or expand the MXML blocks, but they are working wrong !

If you click the element in Outline view, it should highlight the entire tag for you. Is it not doing this in FB 4?

SOAP Response with WS-Addressing elements

Hi All,
I have an issue with the response message of SOAP - PI - RFC Sync scenario.
In the request of the SOAP message, we receive following header(WS-Addressing) Elements in the SOAP Header part of the envelope.
<wsa:Action wsu:Id="wssecurity_signature_id_281" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
http://partnername/interfacedetails
</wsa:Action>
<wsa:MessageID wsu:Id="wssecurity_signature_id_285" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
uuid:463BF10F-0126-4000-E000-604DAC152914
</wsa:MessageID>
<wsa:RelatesTo wsu:Id="wssecurity_signature_id_283" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
urn:uuid:02875597AE9A49ABAB1229340545618
</wsa:RelatesTo>
Now the issue is the, our interface partner(who actually sends the SOAP Request), wants SOAP response containing the above WS-Addressing elements.
Is it possible with SAP PI?. Can anybody help me with this.
By the way, our interface( SOAP-PI-RFC Sync ) working fine. We just need these elements inside SOAP Response.
Thanks in advance.
Kind Regards,
Prasad.

Hi Prasad,
I am not sure if the problem is solved.
I guess you are talking about a scenario in which a non-SAP consumer sends a request to SAP ABAP provider. The consumer requests the enabling of WS-Addressing. The answer nothing is required to configure the ABAP provider, which will send back a SOAP response either with WS-A or without depending if WS-A is sent by the consumer or not. That might be the case that you can see these headers with the SXMB_MONI.
Hope this helps.
Regards,
Wei

Issue with soap response

Hi,
Below my SOAP request message..
<?xml version="1.0"?>
<soapenv:Envelope xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:wsa="http://schemas.xmlsoap.org/ws/2003/03/addressing/" xmlns:xsd="http://www.w3.org/2001/XMLSchema/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance/">
<soapenv:Header xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<wsse:Security soap:mustUnderstand="1" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
<wsse:UsernameToken>
<wsse:Username>xxxxx</wsse:Username>
<wsse:Password>xxxxx</wsse:Password>
</wsse:UsernameToken>
</wsse:Security>
</soapenv:Header>
<soapenv:Body xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<ns2:Find__CompIntfc__IDS_RQST_PSR_INQ_CI xmlns="http://xmlns.ing.com/Enterprise/Tools/schemas/EDS_FIND_FLT.V1" xmlns:ns2="http://xmlns.ing.com/Enterprise/Tools/schemas/EDS_FIND_REQ.V1" xmlns:ns3="http://xmlns.ing.com/Enterprise/Tools/schemas/EDS_FIND_RSP.V1" xmlns:ns4="http://xmlns.ing.com/Enterprise/Tools/schemas/EDS_GET_FLT.V1" xmlns:ns5="http://xmlns.ing.com/Enterprise/Tools/schemas/EDS_GET_REQ.V1" xmlns:ns6="http://xmlns.ing.com/Enterprise/Tools/schemas/EDS_GET_RSP.V1">
<ns2:ING_SUSPS_CNTL_NBR>999999999</ns2:ING_SUSPS_CNTL_NBR>
<ns2:IDS_SITE_ID>HFD</ns2:IDS_SITE_ID>
</ns2:Find__CompIntfc__IDS_RQST_PSR_INQ_CI>
</soapenv:Body>
</soapenv:Envelope>
I am getting the below response message... The issue is with namespace in the response (ns2success). I do not know why there is a success word in the namespace which is causing invalid XML message.
<?xml version="1.0"?>
<soapenv:Envelope xmlns:soapenc="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">
<soapenv:Body>
<ns2:Find__CompIntfc__IDS_RQST_PSR_INQ_CIResponse xmlns:ns2Success="http://xmlns.ing.com/Enterprise/Tools/schemas/EDS_FIND_RSP.V1"/>
</soapenv:Body>
</soapenv:Envelope>

I have i fact never seen this before.
On with tools release are you working and wich CI/component are you trying to call.
Also can you verify if the CI is valide, by opening it in Application Designer.
If validate, can you try to test the CI in Application Desiger and invoke the Find method.
If above test fial, fix the CI and regenerate the CI Service.
If both tests run fine, try to delete the WSDL and CI Service and Provide CI Service again.

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

Soap request- XI- RFC- RFC- soap response

Hi,
I want to implement a scenario like this.
A third party system use the soap adapter to call the ECC RFC via XI.
AND I want to write the RFC response into another RFC.
After that i want to send back another Rfc response result to soap client (third party system).
So the scenario looks like this
soap request->XI->RFC->RFC->soap response
I want to use BPM,but have not too much experience.appreciate your help.
Regards

Hi,
You would need a Synch Asynch Bridge in this case.
Steps in BPM.
1. Receive --> Receives SOAP request message --> Select Opens Synch Asynch Bridge
2. Transfrom --> Map SOAP request to RFC 1's request Message
3. Send Synchronous --> Make the Synch Call to the RFC and get the Response back.
4. Transform --> Map RFC 1's response to RFC 2's Request
5. Send Synchronous --> Make the Synch Call to RFC 2 and get the RFC response back
6. Trasnsform -->Map RFC 2's response to SOAP response.
7. Send --> Select Closes Synch Asycnh Bridge and Send SOAP response back.
For synch asynch bridge , take a look at this too,
http://help.sap.com/saphelp_nw04/helpdata/en/83/d2a84028c9e469e10000000a1550b0/content.htm
Regards,
Bhavesh

SOAP response enclosed in XD tags

Hello,
I use this function to make a SOAP request to my server:
function Execute-SOAPRequest
[Xml] $SOAPRequest,
[String] $URL
write-host "Sending SOAP Request To Server: $URL"
$soapWebRequest = [System.Net.WebRequest]::Create($URL)
$soapWebRequest.Headers.Add("SOAPAction","`"`"")
$soapWebRequest.ContentType = "text/xml;charset=`"utf-8`""
$soapWebRequest.Accept = "text/xml"
$soapWebRequest.Method = "POST"
write-host "Initiating Send."
$requestStream = $soapWebRequest.GetRequestStream()
$SOAPRequest.Save($requestStream)
$requestStream.Close()
write-host "Send Complete, Waiting For Response."
$resp = $soapWebRequest.GetResponse()
$responseStream = $resp.GetResponseStream()
$soapReader = [System.IO.StreamReader]($responseStream)
$ReturnXml = [Xml] $soapReader.ReadToEnd()
$responseStream.Close()
write-host "Response Received."
return $ReturnXml
The soap response is well recived but with the command "$ret | Export-Clixml c:\1.xml;Get-Content c:\1.xml",
the XML file contains:
<Objs Version="1.1.0.1" xmlns="http://schemas.microsoft.com/powershell/2004/04">
<XD> ... </XD>
</Objs>
Between XD tags I have my xml reponse received from the server except that "<" and ">" are converted
to the html code, "<" and ">".
I'm using select-string cmdlet with -patern option to check the response, but it would be more convenient to use the xml
way like $ret.SelectNodes()
I tried doing a replace on the response before doing the export-clixml, but it doesnt work, how can I do this ?
Thank you :)

Nice bunch ofgueses but, if you look up the type and see that it has a "save", then you will be able to do this:
Here I show how t use static strings to avoind issues with quotes in HTML and XML strings. In bothe we can use either single or double quotes on attributes.
function Execute-SOAPRequest{
Param(
[xml]$SOAPRequest,
[string] $URL
write-host "Sending SOAP Request To Server: $URL"
$soapWebRequest = [System.Net.WebRequest]::Create($URL)
$soapWebRequest.Headers.Add('SOAPAction','""')
$soapWebRequest.ContentType = 'text/xml;charset="utf-8"'
$soapWebRequest.Accept = 'text/xml'
$soapWebRequest.Method = 'POST'
write-host 'Initiating Send.'
$requestStream = $soapWebRequest.GetRequestStream()
$SOAPRequest.Save($requestStream)
$requestStream.Close()
write-host 'Send Complete, Waiting For Response.'
$resp = $soapWebRequest.GetResponse()
$responseStream = $resp.GetResponseStream()
$soapReader = [System.IO.StreamReader]($responseStream)
$ReturnXml = [Xml]$soapReader.ReadToEnd()
$responseStream.Close()
write-host 'Response Received.'
$ReturnXml
# to save
$xml=Execute-SOAPRequest $request $uri
$xml.Save('c:\mysoap.xml')
Export-CliXml is used to persist PS objects. It does not ssabe XML objects as an XML file.
Use [xml] to reload tehfile
You should use New-WebServiceProxy as it does all of this for you.
$URI = "http://www.webservicex.net/uszip.asmx?WSDL"
$zip = New-WebServiceProxy -Uri $URI
$xmlResponse=$zip.GetInfoByAreaCode(212)
$xmlResponse.Table | ft -auto
$xml=[xml]('<ac212>'+$xmlResponse.InnerXml.ToString()+'</ac212>')
$xml.Save('c:\AC212.xml')
¯\_(ツ)_/¯

Valid SOAP response

Hi All,
I have a problem with a webservice response. I need to invoke a webservice (binary implementation is different) that is located in two seperate servers (binary implementation is different). Each webservice has the same interface for both the request and the response. My cliente (calling code) is using the Java API for XML-based RPC (JAX-RPC) and is implemented using weblogic server 7.0 to invoke the two web services. I can invoke correctly one of the web services but I get an error with the other one.
I have seen in other forums that weblogic requires a property passed in when you start weblogic called:
weblogic.webservice.i18n.charset=UTF-8 -Dfile.encoding=ISO-8859-1
where I pass in like
'Dweblogic.webservice.i18n.charset=UTF-8 -Dfile.encoding=ISO-8859-1'
but this has not solved the problem.
Questions:
1: Does the WSDL have to be the same for the two web services ?
2: Is it a problem with the response (XML) or a communication error ?
Thanking you in advance,
Nacho
PD: The error I get is:
com.amena.sgp.funcionalidades.incidencias.excepciones.ErrorEnvioEstado: Error reading the response from: https://ws/webservice/gi. Please ensure that this is a valid SOAP response. The message was:
<env:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"><env:Header></env:Header><env:Body><m:gi-aperturaResponse xmlns:m="urn:pm_gi_interfaz_soap2" env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><result xmlns:ns100="urn:pm_gi_interfaz_soap2" xsi:type="ns100:gi-resp-t"><cod-respuesta xsi:type="xsd:string">05000</cod-respuesta><des-respuesta xsi:type="xsd:string">Ok. Ejecuci?n correcta de la operaci?n.</des-respuesta></result></m:gi-aperturaResponse></env:Body></env:Envelope>
at com.amena.sgp.webservice.incidencias.proxy.IncidenciasWSProxy.abrirIncidencia(IncidenciasWSProxy.java:316)
at com.amena.sgp.funcionalidades.incidencias.IncidenciaEmisor.abrirPendiente(IncidenciaEmisor.java:466)
at com.amena.sgp.funcionalidades.incidencias.IncidenciaEmisor.abrirIncidencia(IncidenciaEmisor.java:129)
at com.amena.sgp.funcionalidades.incidencias.FactoriaIncidencias.obtenerIncidencia(FactoriaIncidencias.java:117)
at com.amena.sgp.factoria.comandos.incidencias.CmdCrearIncidenciaEmisor.ejecutarComando(CmdCrearIncidenciaEmisor.java:169)
at com.amena.sgp.servlets.Controlador.doGet(Controlador.java:147)
at com.amena.sgp.servlets.Controlador.doPost(Controlador.java:218)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run(ServletStubImpl.java:1075)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:418)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:306)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:5517)
at weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:685)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:3156)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:2506)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:234)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:210)
and :
unknown attr1.3.6.1.4.1.311.17.1

<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>
</env:Header>
<env:Body>
<m:gi-apertura xmlns:m="urn:pm_gi_interfaz_soap2"
env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<cod-usuario xsi:type="xsd:string"></cod-usuario>
<tex-password xsi:type="xsd:string"></tex-password>
<cod-usuactuacion xsi:type="xsd:string">Administrador</cod-usuactuacion>
<cod-incidencia xsi:type="xsd:string">AME-6002-000000061</cod-incidencia>
<tip-asociado xsi:type="xsd:string">M</tip-asociado>
<tex-asociado xsi:nil="true">
</tex-asociado>
<fec-actuacion xsi:type="xsd:string">29/08/2005 14:58:43</fec-actuacion>
<lst-msisdn>
<item>
</item>
</lst-msisdn>
<tex-incidencia xsi:type="xsd:string">Prueba de sistemas.</tex-incidencia>
</m:gi-apertura>
</env:Body>
</env:Envelope>Handshake finished!
CipherSuite:SSL_RSA_WITH_RC4_128_MD5
SessionId [Session-2, SSL_RSA_WITH_RC4_128_MD5]
PeerHost www.portabilidad.vodafone.es
java.io.CharConversionException: Illegal ASCII character, 0xf3
at weblogic.xml.babel.reader.XmlReader$AsciiReader.read(XmlReader.java:824)
at weblogic.xml.babel.scanner.ScannerState.read(ScannerState.java:382)
at weblogic.xml.babel.scanner.ScannerState.expect(ScannerState.java:235)
at weblogic.xml.babel.scanner.CloseTag.read(CloseTag.java:21)
at weblogic.xml.babel.scanner.Scanner.startState(Scanner.java:226)
at weblogic.xml.babel.scanner.Scanner.scan(Scanner.java:153)
at weblogic.xml.babel.baseparser.BaseParser.prime(BaseParser.java:243)
at weblogic.xml.babel.baseparser.BaseParser.initScanner(BaseParser.java:107)
at weblogic.xml.babel.baseparser.BaseParser.init(BaseParser.java:222)
at weblogic.xml.babel.baseparser.BaseParser.init(BaseParser.java:101)
at weblogic.xml.babel.parsers.XMLInputStreamParser.<init>(XMLInputStreamParser.java:35)
at weblogic.xml.babel.stream.XMLInputStreamBase.open(XMLInputStreamBase.java:64)
at weblogic.xml.babel.stream.XMLInputStreamBase.open(XMLInputStreamBase.java:48)
at weblogic.xml.babel.stream.XMLInputStreamFactoryImpl.newInputStream(XMLInputStreamFactoryImpl.java:66)
at weblogic.xml.babel.stream.XMLInputStreamFactoryImpl.newInputStream(XMLInputStreamFactoryImpl.java:53)
at weblogic.xml.stream.util.RecyclingFactory.remove(RecyclingFactory.java:95)
at weblogic.xml.stream.util.RecyclingFactory.remove(RecyclingFactory.java:128)
at weblogic.webservice.core.soap.SOAPEnvelopeImpl.<init>(SOAPEnvelopeImpl.java:165)
at weblogic.webservice.core.soap.SOAPPartImpl.<init>(SOAPPartImpl.java:104)
at weblogic.webservice.core.soap.SOAPMessageImpl.<init>(SOAPMessageImpl.java:113)
at weblogic.webservice.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:27)
at weblogic.webservice.binding.soap.HttpClientBinding.receive(HttpClientBinding.java:185)
at weblogic.webservice.core.handler.ClientHandler.handleResponse(ClientHandler.java:57)
at weblogic.webservice.core.HandlerChain.handleResponse(HandlerChain.java:199)
at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:435)
at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:360)
at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:441)
at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:310)
at com.amena.sgp.webservice.incidencias.proxy.IncidenciasWSProxy.abrirIncidencia(IncidenciasWSProxy.java:284)
at com.amena.sgp.webservice.incidencias.rmi.IncidenciasServer.abrirIncidencia(IncidenciasServer.java:54)
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 sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:261)
at sun.rmi.transport.Transport$1.run(Transport.java:148)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:144)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701)
at java.lang.Thread.run(Thread.java:536)
amount read:0inputBufferSize512overflow256
Error at line:1 col:562 Got character[0] expected a valid XML character
at weblogic.xml.babel.scanner.ScannerState.checkedRead(ScannerState.java:594)
at weblogic.xml.babel.scanner.CharData.read(CharData.java:65)
at weblogic.xml.babel.scanner.Scanner.startState(Scanner.java:265)
at weblogic.xml.babel.scanner.Scanner.scan(Scanner.java:153)
at weblogic.xml.babel.baseparser.BaseParser.accept(BaseParser.java:451)
at weblogic.xml.babel.baseparser.StartElement.parse(StartElement.java:77)
at weblogic.xml.babel.baseparser.BaseParser.parseElement(BaseParser.java:381)
at weblogic.xml.babel.baseparser.BaseParser.parseSome(BaseParser.java:278)
at weblogic.xml.babel.parsers.XMLInputStreamParser.internalParseSome(XMLInputStreamParser.java:120)
at weblogic.xml.babel.parsers.XMLInputStreamParser.streamParseSome(XMLInputStreamParser.java:135)
at weblogic.xml.babel.stream.XMLInputStreamBase.peek(XMLInputStreamBase.java:203)
at weblogic.xml.stream.util.XMLInputStreamFilterBase.hasNext(XMLInputStreamFilterBase.java:55)
at weblogic.webservice.xml.XMLNode.readChildren(XMLNode.java:714)
at weblogic.webservice.xml.XMLNode.read(XMLNode.java:664)
at weblogic.webservice.xml.XMLNode.readChildren(XMLNode.java:722)
at weblogic.webservice.xml.XMLNode.read(XMLNode.java:664)
at weblogic.webservice.xml.XMLNode.readChildren(XMLNode.java:722)
at weblogic.webservice.xml.XMLNode.read(XMLNode.java:664)
at weblogic.webservice.xml.XMLNode.readChildren(XMLNode.java:722)
at weblogic.webservice.xml.XMLNode.read(XMLNode.java:664)
at weblogic.webservice.core.soap.SOAPEnvelopeImpl.<init>(SOAPEnvelopeImpl.java:166)
at weblogic.webservice.core.soap.SOAPPartImpl.<init>(SOAPPartImpl.java:104)
at weblogic.webservice.core.soap.SOAPMessageImpl.<init>(SOAPMessageImpl.java:113)
at weblogic.webservice.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:27)
at weblogic.webservice.binding.soap.HttpClientBinding.receive(HttpClientBinding.java:185)
at weblogic.webservice.core.handler.ClientHandler.handleResponse(ClientHandler.java:57)
at weblogic.webservice.core.HandlerChain.handleResponse(HandlerChain.java:199)
at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:435)
at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:360)
at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:441)
at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:310)
at com.amena.sgp.webservice.incidencias.proxy.IncidenciasWSProxy.abrirIncidencia(IncidenciasWSProxy.java:284)
at com.amena.sgp.webservice.incidencias.rmi.IncidenciasServer.abrirIncidencia(IncidenciasServer.java:54)
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 sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:261)
at sun.rmi.transport.Transport$1.run(Transport.java:148)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:144)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701)
at java.lang.Thread.run(Thread.java:536)
--------------- nested within: ------------------
weblogic.xml.stream.XMLStreamException: Got character[0] expected a valid XML character - with nested exception:
[Error at line:1 col:562 Got character[0] expected a valid XML character]
at weblogic.xml.babel.adapters.XMLInputStreamElementFactory.create(XMLInputStreamElementFactory.java:106)
at weblogic.xml.babel.parsers.XMLInputStreamParser.internalParseSome(XMLInputStreamParser.java:123)
at weblogic.xml.babel.parsers.XMLInputStreamParser.streamParseSome(XMLInputStreamParser.java:135)
at weblogic.xml.babel.stream.XMLInputStreamBase.peek(XMLInputStreamBase.java:203)
at weblogic.xml.stream.util.XMLInputStreamFilterBase.hasNext(XMLInputStreamFilterBase.java:55)
at weblogic.webservice.xml.XMLNode.readChildren(XMLNode.java:714)
at weblogic.webservice.xml.XMLNode.read(XMLNode.java:664)
at weblogic.webservice.xml.XMLNode.readChildren(XMLNode.java:722)
at weblogic.webservice.xml.XMLNode.read(XMLNode.java:664)
at weblogic.webservice.xml.XMLNode.readChildren(XMLNode.java:722)
at weblogic.webservice.xml.XMLNode.read(XMLNode.java:664)
at weblogic.webservice.xml.XMLNode.readChildren(XMLNode.java:722)
at weblogic.webservice.xml.XMLNode.read(XMLNode.java:664)
at weblogic.webservice.core.soap.SOAPEnvelopeImpl.<init>(SOAPEnvelopeImpl.java:166)
at weblogic.webservice.core.soap.SOAPPartImpl.<init>(SOAPPartImpl.java:104)
at weblogic.webservice.core.soap.SOAPMessageImpl.<init>(SOAPMessageImpl.java:113)
at weblogic.webservice.core.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:27)
at weblogic.webservice.binding.soap.HttpClientBinding.receive(HttpClientBinding.java:185)
at weblogic.webservice.core.handler.ClientHandler.handleResponse(ClientHandler.java:57)
at weblogic.webservice.core.HandlerChain.handleResponse(HandlerChain.java:199)
at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:435)
at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:360)
at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:441)
at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:310)
at com.amena.sgp.webservice.incidencias.proxy.IncidenciasWSProxy.abrirIncidencia(IncidenciasWSProxy.java:284)
at com.amena.sgp.webservice.incidencias.rmi.IncidenciasServer.abrirIncidencia(IncidenciasServer.java:54)
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 sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:261)
at sun.rmi.transport.Transport$1.run(Transport.java:148)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:144)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701)
at java.lang.Thread.run(Thread.java:536)
<Aug 29, 2005 2:58:48 PM MEST> <Info> <webservice> <220025> <Handler weblogic.webservice.core.handler.ClientHandler threw an exception from its handleResponse method. The exception was:
javax.xml.rpc.JAXRPCException: java.io.IOException: Error reading the response from: https://www.xxx.xxxx. Please ensure that this is a valid SOAP response. The message was:
<env:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"><env:Header></env:Header><env:Body><m:gi-aperturaResponse xmlns:m="urn:pm_gi_interfaz_soap2" env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><result xmlns:ns100="urn:pm_gi_interfaz_soap2" xsi:type="ns100:gi-resp-t"><cod-respuesta xsi:type="xsd:string">05000</cod-respuesta><des-respuesta xsi:type="xsd:string">Ok. Ejecuci?n correcta de la operaci?n.</des-respuesta></result></m:gi-aperturaResponse></env:Body></env:Envelope>>

<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>
</env:Header>
<env:Body>
<env:Fault>
<faultcode>env:Server</faultcode>
<faultstring>Error reading the response from: https://xxx.xxx.xxx/wwww. Please ensure that this is a valid SOAP response. The message was:
<env:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"><env:Header></env:Header><env:Body><m:gi-aperturaResponse xmlns:m="urn:pm_gi_interfaz_soap2" env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><result xmlns:ns100="urn:pm_gi_interfaz_soap2" xsi:type="ns100:gi-resp-t"><cod-respuesta xsi:type="xsd:string">05000</cod-respuesta><des-respuesta xsi:type="xsd:string">Ok. Ejecuci?n correcta de la operaci?n.</des-respuesta></result></m:gi-aperturaResponse></env:Body></env:Envelope></faultstring>
<detail>
<bea_fault:stacktrace xmlns:bea_fault="http://www.bea.com/servers/wls70/webservice/fault/1.0.0">java.io.IOException: Error reading the response from: https://www.xxx.xxxe. Please ensure that this is a valid SOAP response. The message was:
<env:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"><env:Header></env:Header><env:Body><m:gi-aperturaResponse xmlns:m="urn:pm_gi_interfaz_soap2" env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><result xmlns:ns100="urn:pm_gi_interfaz_soap2" xsi:type="ns100:gi-resp-t"><cod-respuesta xsi:type="xsd:string">05000</cod-respuesta><des-respuesta xsi:type="xsd:string">Ok. Ejecuci?n correcta de la operaci?n.</des-respuesta></result></m:gi-aperturaResponse></env:Body></env:Envelope>
at weblogic.webservice.binding.soap.HttpClientBinding.receive(HttpClientBinding.java:189)
at weblogic.webservice.core.handler.ClientHandler.handleResponse(ClientHandler.java:57)
at weblogic.webservice.core.HandlerChain.handleResponse(HandlerChain.java:199)
at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:435)
at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:360)
at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:441)
at weblogic.webservice.core.rpc.CallImpl.invoke(CallImpl.java:310)
at com.amena.sgp.webservice.incidencias.proxy.IncidenciasWSProxy.abrirIncidencia(IncidenciasWSProxy.java:284)
at com.amena.sgp.webservice.incidencias.rmi.IncidenciasServer.abrirIncidencia(IncidenciasServer.java:54)
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 sun.rmi.server.UnicastServerRef.dispatch(UnicastServerRef.java:261)
at sun.rmi.transport.Transport$1.run(Transport.java:148)
at java.security.AccessController.doPrivileged(Native Method)
at sun.rmi.transport.Transport.serviceCall(Transport.java:144)
at sun.rmi.transport.tcp.TCPTransport.handleMessages(TCPTransport.java:460)
at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(TCPTransport.java:701)
at java.lang.Thread.run(Thread.java:536)
</bea_fault:stacktrace>
</detail>
</env:Fault>
</env:Body>
</env:Envelope>

I'm having the same problem. We were calling the service via weblogic.jws.proxies. , after moving end point to another host in other lan (tunneled to old end point )
After this we can't invoke old methods all we got is this exception
<env:Envelope xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/"
xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<env:Header>
</env:Header>
<env:Body>
<env:Fault>
<faultcode>env:Server</faultcode>
<faultstring>Error reading the response from: http://fire.unx.era.pl:7778/adPrm/ServicesForPRM/WS-Impl/FetchAtmosferaRejectableGroups. Please ensure that this is a valid SOAP response. The message was:
<?xml version="1.0" encoding="UTF-8"?><SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"><SOAP-ENV:Body><ns0:fetchAtmosferaRejectableGroupsResponse xmlns:ns0="http://www.computerland.pl/xsd/matrix/ws/"><ns0:result><ns0:errCode>0</ns0:errCode><ns0:errDesc>OK</ns0:errDesc></ns0:result><ns0:groupList><ns0:group name="Poczta/Domena/Terminale/CIS/DokE/Intranet, II linia"/><ns0:group name="IPS HelpDesk, II linia"/><ns0:group name="Telekomunikacja Help, II linia"/><ns0:group name="SAP Help, II linia"/><ns0:group name="CS Technical Support"/><ns0:group name="Interfejsy z Sieci?? Telekom, III linia"/><ns0:group name="Billing Analiza i Rozw??j, III linia"/><ns0:group name="Customer Care Analiza i Rozw??j, III Linia"/><ns0:group name="SAP Analiza i Rozw??j Admin, III linia"/><ns0:group name="Systemy Wspomagania Sieci ERA AiR, III linia"/><ns0:group name="CIS Sekcja Budowy Hurtowni Danych, III linia"/><ns0:group name="CIS Sekcja Budowy Aplikacji Analitycznych, III linia"/><ns0:group name="Intranet Analiza i Rozw??j, III linia"/><ns0:group name="Dok Elektr i Workflow AiR, III linia"/><ns0:group name="Sekcja Nadzoru Operacyjnego, III Linia"/><ns0:group name="Sekcja Test??w System??w, III Linia"/><ns0:group name="Telekomunikacja AiR, III linia"/><ns0:group name="PC Analiza i Rozw??j, III linia"/><ns0:group name="PC Zesp???? Bezpiecze??stwa Syst"/><ns0:group name="Oracle i Unix Administracja, III Linia"/><ns0:group name="Operatorzy, Sekcja Obs??ugi System??w"/><ns0:group name="Administratorzy Siec Syst Komp, III linia"/><ns0:group name="Billing & CustomerCare Support, II linia"/><ns0:group name="Sekcja Nadzoru Aplikacji, III Linia"/><ns0:group name="TIBCO Analiza i Rozw??j, III linia"/><ns0:group name="Region Katowice"/><ns0:group name="Region Gda??sk"/><ns0:group name="Region Pozna??"/><ns0:group name="Region Warszawa"/><ns0:group name="Sekcja Ochrony Danych, Pion Administracji"/><ns0:group name="PC Helpdesk, II linia"/></ns0:groupList></ns0:fetchAtmosferaRejectableGroupsResponse></SOAP-ENV:Body></SOAP-ENV:Envelope></faultstring>
<detail>
<bea_fault:stacktrace xmlns:bea_fault="http://www.bea.com/servers/wls70/webservice/fault/1.0.0">java.io.IOException: Error reading the response from: http://fire.unx.era.pl:7778/adPrm/ServicesForPRM/WS-Impl/FetchAtmosferaRejectableGroups. Please ensure that this is a valid SOAP response. The message was:
<?xml version="1.0" encoding="UTF-8"?><SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"><SOAP-ENV:Body><ns0:fetchAtmosferaRejectableGroupsResponse xmlns:ns0="http://www.computerland.pl/xsd/matrix/ws/"><ns0:result><ns0:errCode>0</ns0:errCode><ns0:errDesc>OK</ns0:errDesc></ns0:result><ns0:groupList><ns0:group name="Poczta/Domena/Terminale/CIS/DokE/Intranet, II linia"/><ns0:group name="IPS HelpDesk, II linia"/><ns0:group name="Telekomunikacja Help, II linia"/><ns0:group name="SAP Help, II linia"/><ns0:group name="CS Technical Support"/><ns0:group name="Interfejsy z Sieci?? Telekom, III linia"/><ns0:group name="Billing Analiza i Rozw??j, III linia"/><ns0:group name="Customer Care Analiza i Rozw??j, III Linia"/><ns0:group name="SAP Analiza i Rozw??j Admin, III linia"/><ns0:group name="Systemy Wspomagania Sieci ERA AiR, III linia"/><ns0:group name="CIS Sekcja Budowy Hurtowni Danych, III linia"/><ns0:group name="CIS Sekcja Budowy Aplikacji Analitycznych, III linia"/><ns0:group name="Intranet Analiza i Rozw??j, III linia"/><ns0:group name="Dok Elektr i Workflow AiR, III linia"/><ns0:group name="Sekcja Nadzoru Operacyjnego, III Linia"/><ns0:group name="Sekcja Test??w System??w, III Linia"/><ns0:group name="Telekomunikacja AiR, III linia"/><ns0:group name="PC Analiza i Rozw??j, III linia"/><ns0:group name="PC Zesp???? Bezpiecze??stwa Syst"/><ns0:group name="Oracle i Unix Administracja, III Linia"/><ns0:group name="Operatorzy, Sekcja Obs??ugi System??w"/><ns0:group name="Administratorzy Siec Syst Komp, III linia"/><ns0:group name="Billing & CustomerCare Support, II linia"/><ns0:group name="Sekcja Nadzoru Aplikacji, III Linia"/><ns0:group name="TIBCO Analiza i Rozw??j, III linia"/><ns0:group name="Region Katowice"/><ns0:group name="Region Gda??sk"/><ns0:group name="Region Pozna??"/><ns0:group name="Region Warszawa"/><ns0:group name="Sekcja Ochrony Danych, Pion Administracji"/><ns0:group name="PC Helpdesk, II linia"/></ns0:groupList></ns0:fetchAtmosferaRejectableGroupsResponse></SOAP-ENV:Body></SOAP-ENV:Envelope>
at weblogic.webservice.binding.soap.HttpClientBinding.receive(HttpClientBinding.java:195)
at weblogic.webservice.core.handler.ClientHandler.handleResponse(ClientHandler.java:57)
at weblogic.webservice.core.HandlerChain.handleResponse(HandlerChain.java:199)
at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:456)
at weblogic.webservice.core.DefaultOperation.invoke(DefaultOperation.java:377)
at weblogic.webservice.core.rpc.StubImpl._invoke(StubImpl.java:244)
at weblogic.jws.proxies.FetchAtmosferaRejectableGroups_PortType_Stub.fetchAtmosferaRejectableGroups(FetchAtmosferaRejectableGroups_PortType_Stub.java:33)
at pl.era.prime.integration.client.AtmPCHS2PrimeBean.FetchAtmosferaRejectableGroups(AtmPCHS2PrimeBean.java:167)
at pl.era.prime.integration.client.AtmPCHS2PrimeSession_lm80md_EOImpl.FetchAtmosferaRejectableGroups(AtmPCHS2PrimeSession_lm80md_EOImpl.java:46)
at pl.era.prime.integration.client.AtmPCHS2PrimeSession_lm80md_EOImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:455)
at weblogic.rmi.cluster.ReplicaAwareServerRef.invoke(ReplicaAwareServerRef.java:114)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:396)
at weblogic.security.service.SecurityServiceManager.runAs(SecurityServiceManager.java:726)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:391)
at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest.java:30)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:251)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:219)
</bea_fault:stacktrace>
</detail>
</env:Fault>
</env:Body>
</env:Envelope>
I suppose the problem is in setting end point for back response, has any one similar problem ??

MessageHandlers - caching of SOAP responses

I have a webservice which has a number of clients who will all consume the same
message once. I've determined that one of my bottlenecks is actually turning
the results of the EJB call into the SOAP message. Since all the clients will
receive the same message once I think it would be nice to cache the soap message
resulting from a call.
Can I use a message handler to do this, or will the SOAP message already have
been generated?

Hi Tom,
Your previous reply clears things up :-) But for the record, serialization (converting
the value returned from the EJB to XML) has already occurred when the handleResponse(MessageContext)
method is called. That's why you can get access to (and manipulate) the SOAP response
in the handleResponse(MessageContext) method. This SOAP response has the value
returned from the EJB in it, when the handleResponse(MessageContext) method is
called.
Later,
Mike Wooten
"Tom Hennen" <[email protected]> wrote:
>
I need to call the EJB because what it returns will determine if the
message is
already cached. You see the ejb returns a message from a queue. That
message
needs to be removed from the queue, and the handler won't know if it
has the message
cached until it gets a response from the EJB.
At any rate it sounds like you're saying the serialization takes place
after handlerResponse
gets through with the Message? If that's the case then this won't work
anyways.
"Michael Wooten" <[email protected]> wrote:
Hi Tom,
You'd have to store something in the MessageContext DURING the handleRequest(MessageContext)
method processing, to make any sense here :-)
The JAX-RPC Handler infrastructure is only guaranteeing that the property
stored
during the handleRequest(MessageContext) call, will be available during
the handleResponse(MessageContext)
call.
I don't quite understand why you need to call the EJB, if you already
know what
the value of the return object will be. I'm assuming that the EJB will
return
the same result, for a given value assigned to the input arguments.If
this is
true, why can't you use a byte[] created from the payload of the <SOAPBody>
request,
as the cache item key. If you don't find the cache item key (you look
in the
handleRequest method), set a MessageContext property with the payload
byte[],
and call the EJB. When the EJB returns, retrieve the property and use
it to create
a cache item that has the value of the property as the key, and a byte[]
of the
SOAP response as a value. When the handleResponse method is called,it
will contain
the response that will become the cache item value. Create a byte[]from
it, assign
the value of the property as the key, and a byte[] of the SOAP response
as the
value. If you find the key in the cache during the handleRequest(MessageContext)
call, retreive the cache value, put it in a MessageContext property,
return false
from handleRequest(MessageContext), grab the MessageContext property
value in
the handleResponse(MessageContext) method, and create the SOAP response
with it.
I take it that this isn't something you can do in your situation :-)
Calling the EJB from inside the handleRequest(MessageContext) method
will still
have performance issues, because you'll still need to deal with serializing/deserializing
XML.
Regards,
Mike Wooten
"Tom Hennen" <[email protected]> wrote:
Hmm, that's what I was afraid of.
We actually have to call the EJB. Skipping it isn't an option.
The
ejb only
accesses data in memory, so caching it's response would be of little
value anyways.
When using RMI to bypass the jax-rpc stack I'm seeing CPU usage about
1/3 less
than when using webservices. Overall throughput also more than doubles.
Would I see a benefit to calling the EJB from the handleRequest method
and then
based upon it's response sticking a cached SOAP message into the message
context?
Of course this would bring up the problem of what to do if the message
hasn't
been cached (calling the EJB twice isn't allowed).
"Michael Wooten" <[email protected]> wrote:
Hi Tom,
The SOAP message will have already been created for both client andserver-side
JAX-RPC Handlers, but you can avoid the EJB call :-)
The flow is as follows:
1. Web service consumer code calls web service operation.
2. The client-side JAX-RPC stack creates a SOAP message from the call.
If a
client-side JAX-RPC Handler is in place for the called operation,
it's
handleRequest
callback method is invoked.
3. If handleRequest returns a true, or there is no client-side JAX-RPC
Handler
in place, the
JAX-RPC implementation connects to the endpoint URL and sends the
SOAP
message.
4. The server-side JAX-RPC stack invokes the handleRequest method,of
a server-side
JAX-RPC Handler for the operation, if one is defined. It (the server-side
JAX-RPC
stack) hasn't made the call to the EJB that is providing the service
implementation
yet.
NOTE: Seeing as the EJB hasn't been called yet, you could have thecode
in the
handleRequest method return a cached response. The assumption here,would
be that
this server-side JAX-RPC Handler had access to a shared database (or
a JCache-based
product), that it could query in the handleRequest method, and update
in the handleResponse
method. If the query returned a cached SOAP response, you would useit
to set
a property on the MessageContext object passed to handleRequest, using
the setProperty
method, and return false from handleRequest. The stack should then
bypass
invoking
the EJB and call the handleResponse, using the same MessageContextobject
you
set the property on in the handleRequest method. Call the getProperty
on the MessageContext
object in the handleResponse method, to get the cached SOAP response,
and use
it to replace the one currently in the SOAP response. If performance
is a major
factor (which sounds like the case), you might want to replace theshared
database
with an distributed cache product (i.e. Tangosol Coherence, an open-source
JCache
product, etc.), or an XML database :-)
5. If the handleRequest method of the server-side JAX-RPC Handler
returns
true,
or no server-side JAX-RPC Handler was defined for the operation, the
server-side
stack calls the EJB.
6. If a server-side JAX-RPC Handler is defined, the server-side stack
calls the
handleResponse method. If not, the stack uses the results of the EJB
call to create
the SOAP response.
7. If a client-side JAX-RPC Handler is defined, the client-side stack
calls the
handleResponse method. Afterwards, it processes the SOAP responseand
deserializes
the return value. If no client-side JAX-RPC Handler is defined, theclient-side
stack just processes the SOAP response and deserializes the return
value.
HTH,
Mike Wooten
"Tom Hennen" <[email protected]> wrote:
I have a webservice which has a number of clients who will all consume
the same
message once. I've determined that one of my bottlenecks is actually
turning
the results of the EJB call into the SOAP message. Since all the
clients
will
receive the same message once I think it would be nice to cache thesoap
message
resulting from a call.
Can I use a message handler to do this, or will the SOAP message
already
have
been generated?

Font usage in CS6 Premiere , Open and Closed quotes??

Hello
I am trying to use open and closed quotes in CS6 Premiere, without any success.
Using a Mac 10.8.5.
When I try the alt shft [ and the shift [ it only uses one side of the quote.
Any suggestions?
Is this a software, settings or OS issue?
Thank you
I am working on deadline....
Brian

One side? I'm confused. You mean want these?
But you're only seeing this?

I have model A1458...been acting possessed.... apps opening and closing on their own...zooming in and out... not always responsive to my touch... what could be the problem?

i have model A1458...been acting possessed.... apps opening and closing on their own...zooming in and out... not always responsive to my touch... what could be the problem?

The two most likely culprits would be a faulty cable/charging block or a bad digitizer. Try charging the device with a different charger and cable. If the problem goes away, then the problem is with your charger. If it does not, try the basics of resetting, restoriing from back up, restoring as new. If you still have the problem, make an appointment at the Genius Bar at your local Apple Store for evaluation.

Error:SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server was unable to read request. --- There is an error in XML document (1, 447). --- Input string was not in a correct format.

Hi All,
We have a scenario of FTP-->PI---> Webservice. While triggering the data in the FTP, it is failing in the PI with the below error
SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAP_EXCEPTION - soap fault: Server was unable to read request. ---> There is an error in XML document (1, 447). ---> Input string was not in a correct format.
Can you please help?

Hi Raja- It seems to be a data quality issue.
Check for the value @ 1447 position in the xml message that you are trying to send to web service..
may be a date filed/decimal value which is not in expected format.

SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPT

Hi there,
I am trying to publish a file from SAP as web service using XI and SOAP Adapter.
I am using ABAP proxy to get the data into XI.
Designing and Configuration in XI has no problems because when i use File adapter the data is trasmitted to FTP server.
But when I used SOAP Reciever adapter I am getting following error in RWB
Delivery of the message to the application using connection SOAP_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Error during parsing of SOAP header.
Scenario: SAP ABAP Proxy -> XI -> WebService. Asynchronous.
SOAP Receiver adaptor.
Target URL http://<host>:<port number >/sap/xi/engine?type=entry&version=3.0&Sender.Service=SAPDC2653&Interface=urn:bzttest:00:hsa:test%5EOB_MI_BZT_TEST&QualityOfService=ExactlyOnce
Do not use SOAP Envelop is checked.
SOAP Action http://sap.com/xi/WebService/soap1.1
What i am missing here? How should I solve this problem?
Any help is appreciated,
Thx,
Yogi

Say there's a bapi/rfc that you want to call on an R/3 backend (e.g. 4.6c). On it's own, the R/3 system cannot expose the rfc/bapi as a web service, but XI can. So in this case, the scenario would be:
WS client -> XI -> R/3
When XI "exposes" a web service, it is exposing a service for a receiving system (in the above example, the R/3 system). XI itself does not provide or contain the service implementation. When XI exposes a web service, it is always done via the sender soap adapter (i.e. if soap adapter is used). Receiver soap adapter is used to call or consume an actual web service from an external application.
Regards,
Jin

SOAP : response message contains an error Application/UNKNOWN/APPLICATION_E

Hi All,
I am working in a Proxy to SOAP synchronous scenario. Message is processing successfully through IE but i am getting the below error in receiver (SOAP) communication channel.
SOAP : response message contains an error Application/UNKNOWN/APPLICATION_ERROR.
Please suggest what will be possible way out to resolve this issue.
Thanks,
Priya Ranjan

Dear Priya
Have you configured Fault Message for this scenario.
This kind of error is generally thrown by the end target system where the message is not processed succesfully due to some error in there system.
Sourabh

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

SOAP Response conatins no quots, no opening or closing tags.

Similar Messages

Maybe you are looking for