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: <B>Symbol <xsl:value-of select="EmpName"/></B>
</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

Similar Messages

Synchronous RFC -- SOAP Scenario: problem with SOAP Response/Fault Mapping

Hi,
I've a synchronous RFC --> PI --> SOAP Scenario. The problem is that the message structure of the sending RFC doesn't match the Webservice Structure.
The (SAP standard) RFC has just a Request / Response message structure. Part of the Response Message structure is a exception structure.
The Webservice has a Request / Response message structure and in case of an error I get a SOAP:Fault.
Problem now is that I cannot configure that scenario without usage of BPM as I will have to map SOAP:Response or SOAP:Fault to the RFC Response structure.
Has anybody another idea to do that synchronous scenario (with usage of message mapping) without BPM?
BR
Holger

1)
you maus define 3 mapping.
1)request
2)response
3)Fault
in Interface mapping define at response boths (2-3) mapping. its clear??
2)
otherwise sometjhing is not clear, why do you want fault?? why dont you get only response message. we implement this kind of response:
<response_MT>
<ID> (error ID)
<system> (target system)
<error> (Error Description)
</response>
by this way fault message is not needed. but if you must have it just follow the top of message else, propose second.
Thanks
Rodrigo
Thanks
Rodrigo
Edited by: Rodrigo Pertierra on Feb 25, 2008 11:52 AM

XSL stylesheet transformation of RSS feeds

Does Safari support XSL transformation of RSS feeds? Or does it always override XSL with its own RSS reader format? Details below:
I'm starting to mass-produce RSS feeds for our organization. We just want one file for each purpose which can be universally used in RSS readers, iTunes/other podcatchers, and web browsers. I created an XSL stylesheet for it which works perfectly in Internet Explorer, Opera, and Firefox (current release, anyway!), but Safari always adds the "feed://" prefix and displays it with its blue RSS reader format. Is there no way around this? If I take out the the <rss version="2.0"> header, it works, but then iTunes won't accept it.
Do I have to produce two separate files, the first without the RSS notation for Safari's sake, and the second with the notation for iTunes? That seems like an unnecessary step for us, and confusing for our users. Is there any way around this? I couldn't find any support documents that addressed this directly. Thanks -- Jim

You're getting a URL like this:context.getResourceAsStream("/Web-Inf/viewStudentDetails.xsl")and it looks like the MalformedURL exception is complaining about it. So my first step would be to look at it and see what's wrong with it.

Problem in Soap response

Hi all,
I am working on SOAP sychronous scenario.i.e ,Web services(Axis) to SAP R/3 system and i want the response from SAP R/3 system and it is to be displayed in web client.
In this scenario I am able to send the SOAP message to SAP R/3 system through XI.
I have configured both the sender and reciever SOAP adapters.
The BPM steps are:
1. Receive
2. Synchronous Sender step
3. Send
For this BPM i created 5 interfaces.
1. Request_out
2. Response_in
3. Soap_abs_synch
4. Request_abs
5. Response_abs
Now my question is which interface i have to used to send the request and get the response?
Here i used Request_out and i am able to see the response message from R/3 system in SXMB_MONI.
Could anybody please help me to solve this problem.

Hi,
You would have forgot to map parent node coming after <STATUS>Success</STATUS>
Make sure that you have properly mapped all the parents and there child.
Are you getting the same result while Testing it standalone?
Thanks
Sunil Singh

Mapping problem in SOAP response to RFC response - RFC-XI-SOAP scenario

Hi gurus,
response structure from SOAP is as below (inbound msg - in SXMB_MONI)
MONI and RWB shows successful(I am using graphical mapping)
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <ns0:testrequestResponse xmlns:ns0="conversion" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" Status="Success">
- <ns0:SAP_OUT>
       <ns0:F1 Value="1234" />
       <ns0:F2 Value="2345" />
     - <ns0:SAP_LINES>
         - <ns0:SAP_LINE>
                <ns0:SAP_L Value="1" />
                <ns0:Field5 Value="" />
              - <ns0:SAP_S1>
                       - <ns0:SAP_S>
                               <ns0:ID Value="11111" />
                               <ns0:SAP__NO Value="0001" />
                               <ns0:DATE1 Value="08/15/2008 00:00:00:000" />
                               <ns0:FST/>
                         </ns0:SAP_S>
                </ns0:SAP_S1>
         </ns0:SAP_LINE>
      </ns0:SAP_LINES>
</ns0:SAP_OUT>
</ns0:testrequestResponse>
I make the RFC response with same structure and mapped it but it is not giving the full structure rather it is giving only this (Outbound Msg in SXMB_MONI)
<?xml version="1.0" encoding="UTF-8" ?>
- <ns1:Z_MYRFC.Response xmlns:ns1="urn:sap- com:document:sap:rfc:functions">
<STATUS>Success</STATUS>
</ns1:Z_MYRFC.Response>
what went wrong?

Hi,
You would have forgot to map parent node coming after <STATUS>Success</STATUS>
Make sure that you have properly mapped all the parents and there child.
Are you getting the same result while Testing it standalone?
Thanks
Sunil Singh

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 response Error when processing XML CF.

Hello,
I have problems with soap response and wondered if you could give some advice.
Every time I send my message via soap I get the following error:
com.sap.aii.af.ra.ms.api.RecoverableException: SOAP: response message contains an error XIAdapter/HTTP/ADAPTER.HTTP_EXCEPTION - HTTP 500 Error when processing XML CF.
Is it possible that the communication is aborted and my response message mapping is never started?
(Additional info: I tried to create an integration process and am not able to evaluate the response.)
Thanks a lot for your help.
Regards,
Julia

hi,
do you see any more error details in :
http://xiserver:port/MessagingSystem/monitor
did you check logs in visual admin ?
>>>>Is it possible that the communication is aborted and my response message mapping is never started?
yes - if the response is not ok the mapping may not be started
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

Error on XSLT transforming a SOAP response

Hello,
I am getting error ABAP XML formatting error in XML node of type "element", name: "abap" using my XSLT program.
Here is the XML response (SOURCE) as string.
b60##<?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:execResponse soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns1="http://webservice.hostname.com/"><execReturn xsi:type="xsd:string"><?xml version="1.0" encoding="Shift_JIS" ?><Report><Header><system>ABCWEB</system><dataType>ABCDEFGHIJ</dataType><sendType>response</sendType></Header><Body><SequenceNo>1234567890</SequenceNo><InquiryFactory>ABC</InquiryFactory><ProcessingID></ProcessingID><ProcessingDate>1234567890</ProcessingDate><KeyNo>ABCDEFGHIJ</KeyNo><ProcessingClassify>S</ProcessingClassify><Product>ABCDEFGHIJ</Product><ResponseClassify>0</ResponseClassify><OrderInformation-List><OrderInquiry><TransferNo>1234567890</TransferNo><TransferLineNo>000010</TransferLineNo><CustomerOrderNo>ABCDEFGHIJ</CustomerOrderNo><CustomerOrderLineNo>      </CustomerOrderLineNo><ShipInstructionNo>1234567890</ShipInstructionNo><DropUnitPrice>1234567890</DropUnitPrice><Qty>200</Qty><Amount>6000</Amount><WBSNo>                        </WBSNo><SpecPartNo>ABCDEFGHIJ</SpecPartNo></OrderInquiry></OrderInformation-List><SalesOrderPartNo>ABCDEFGHIJ</SalesOrderPartNo><CatalogPartNo></CatalogPartNo><AgentPartNo>1234567890</AgentPartNo><CustomerPartNo></CustomerPartNo><R3CompanyCD>1000</R3CompanyCD><OrderPlacingCompanyCD>R110011</OrderPlacingCompanyCD><ShipToCD>1234567890</ShipToCD><ShipToCompanyName>SINGAPORE</ShipToCompanyName><ShipToAddress1>ABCDEFGHIJ</ShipToAddress1><ShipToAddress2>ABCDEFGHIJ</ShipToAddress2><ShipToAddress3>SINGSAPORE</ShipToAddress3><ShipToAddress4></ShipToAddress4><ULPort>ABCDEFGHIJ</ULPort><DropCurrency>EUR</DropCurrency><DeliveryAirport>SINGAPORE</DeliveryAirport><DropMethod></DropMethod><SCMCustomer>EA07000442</SCMCustomer><RealShipToCd></RealShipToCd><SOCurrency></SOCurrency><SOPayterm></SOPayterm><LogisticCategory>0</LogisticCategory><SOOrderNo></SOOrderNo><MaterialKeyA1>1234567890</MaterialKeyA1></Body></Report></execReturn></ns1:execResponse></soapenv:Body></soapenv:Envelope>##0####
The above is the result after adding the following modifications in ABAP.
REPLACE ALL OCCURRENCES OF
      '<' IN wf_string1 WITH '<' .
REPLACE ALL OCCURRENCES OF
      '>' IN wf_string1 WITH '>' .
REPLACE ALL OCCURRENCES OF
      '"' IN wf_string1 WITH '"'
I would like to display the result starting from <BODY> as table as shown below.
SequenceNo       1234567890
InquiryFactory       ABC
ProcessingID
ProcessingDate    1234567890
and so on.
I am using the the same ABAP/XSLT program following example /people/durairaj.athavanraja/blog/2004/09/20/consuming-web-service-from-abap
Please let me know what I did wrong.
Tony

I have no idea why this is showing like this, but please bear with me. I tried every way I can to make my reply readable but the text editor is keeping on doing this. So here it goes.
Hi Sandeep,
I tried to debug the CALL transformation. I am getting CX_XSLT_FORMAT_ERROR and when I run the whole program this is the error message "ABAP XML formatting error in XML node of type "element", name: "abap"
Here is my XLST program for the response above.
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="1.0">
<xsl:strip-space elements="*"/>
<xsl:output indent="yes"/>
<xsl:template match="NewDataSet">
        <OUTTAB>
          <xsl:for-each select="Table">
            <OUTTAB1>
              <report>
                <header>
                  <system>
                    <xsl:value-of select="system"/>
                  </system>
                  <dataType>
                    <xsl:value-of select="dataType"/>
                  </dataType>
                  <sendType>
                    <xsl:value-of select="sendType"/>
                  </sendType>
                </header>
                <body>
                  <SequenceNo>
                    <xsl:value-of select="SequenceNo"/>
                  </SequenceNo>
                  <InquiryFactory>
                    <xsl:value-of select="InquiryFactory"/>
                  </InquiryFactory>
                  <ProcessingID>
                    <xsl:value-of select="ProcessingID"/>
                  </ProcessingID>
                  <ProcessingDate>
                    <xsl:value-of select="ProcessingDate"/>
                  </ProcessingDate>
                  <KeyNo>
                    <xsl:value-of select="KeyNo"/>
                  </KeyNo>
                  <ProcessingClassify>
                    <xsl:value-of select="ProcessingClassify"/>
                  </ProcessingClassify>
                  <Product>
                    <xsl:value-of select="Product"/>
                  </Product>
                  <ResponseClassify>
                    <xsl:value-of select="ResponseClassify"/>
                  </ResponseClassify>
                  <OrderInformation-List>
                    <OrderInquiry>
                      <TransferNo>
                        <xsl:value-of select="TransferNo"/>
                      </TransferNo>
                      <TransferLineNo>
                        <xsl:value-of select="TransferLineNo"/>
                      </TransferLineNo>
                      <CustomerOrderNo>
                        <xsl:value-of select="CustomerOrderNo"/>
                      </CustomerOrderNo>
                      <CustomerOrderLineNo>
                        <xsl:value-of select="CustomerOrderLineNo"/>
                      </CustomerOrderLineNo>
                      <ShipInstructionNo>
                        <xsl:value-of select="ShipInstructionNo"/>
                      </ShipInstructionNo>
                      <DropUnitPrice>
                        <xsl:value-of select="DropUnitPrice"/>
                      </DropUnitPrice>
                      <Qty>
                        <xsl:value-of select="Qty"/>
                      </Qty>
                      <Amount>
                        <xsl:value-of select="Amount"/>
                      </Amount>
                      <WBSNo>
                        <xsl:value-of select="WBSNo"/>
                      </WBSNo>
                      <SpecPartNo>
                        <xsl:value-of select="SpecPartNo"/>
                      </SpecPartNo>
                    </OrderInquiry>
                  </OrderInformation-List>
                  <SalesOrderPartNo>
                    <xsl:value-of select="SalesOrderPartNo"/>
                  </SalesOrderPartNo>
                  <CatalogPartNo>
                    <xsl:value-of select="CatalogPartNo"/>
                  </CatalogPartNo>
                  <AgentPartNo>
                    <xsl:value-of select="AgentPartNo"/>
                  </AgentPartNo>
                  <CustomerPartNo>
                    <xsl:value-of select="CustomerPartNo"/>
                  </CustomerPartNo>
                  <R3CompanyCD>
                    <xsl:value-of select="R3CompanyCD"/>
                  </R3CompanyCD>
                  <OrderPlacingCompanyCD>
                    <xsl:value-of select="OrderPlacingCompanyCD"/>
                  </OrderPlacingCompanyCD>
                  <ShipToCD>
                    <xsl:value-of select="ShipToCD"/>
                  </ShipToCD>
                  <ShipToCompanyName>
                    <xsl:value-of select="ShipToCompanyName"/>
                  </ShipToCompanyName>
                  <ShipToAddress1>
                    <xsl:value-of select="ShipToAddress1"/>
                  </ShipToAddress1>
                  <ShipToAddress2>
                    <xsl:value-of select="ShipToAddress2"/>
                  </ShipToAddress2>
                  <ShipToAddress3>
                    <xsl:value-of select="ShipToAddress3"/>
                  </ShipToAddress3>
                  <ShipToAddress4>
                    <xsl:value-of select="ShipToAddress4"/>
                  </ShipToAddress4>
                  <ULPort>
                    <xsl:value-of select="ULPort"/>
                  </ULPort>
                  <DropCurrency>
                    <xsl:value-of select="DropCurrency"/>
                  </DropCurrency>
                  <DeliveryAirport>
                    <xsl:value-of select="DeliveryAirport"/>
                  </DeliveryAirport>
                  <DropMethod>
                    <xsl:value-of select="DropMethod"/>
                  </DropMethod>
                  <SCMCustomer>
                    <xsl:value-of select="SCMCustomer"/>
                  </SCMCustomer>
                  <RealShipToCd>
                    <xsl:value-of select="RealShipToCd"/>
                  </RealShipToCd>
                  <SOCurrency>
                    <xsl:value-of select="SOCurrency"/>
                  </SOCurrency>
                  <SOPayterm>
                    <xsl:value-of select="SOPayterm"/>
                  </SOPayterm>
                  <LogisticCategory>
                    <xsl:value-of select="LogisticCategory"/>
                  </LogisticCategory>
                  <SOOrderNo>
                    <xsl:value-of select="SOOrderNo"/>
                  </SOOrderNo>
                  <MaterialKeyA1>
                    <xsl:value-of select="MaterialKeyA1"/>
                  </MaterialKeyA1>
                </body>
              </report>
            </OUTTAB1>
          </xsl:for-each>
        </OUTTAB>
</xsl:template>
</xsl:stylesheet>
Also I noticed that the actual response has two version header. Would it matter? Do I need to crop this out from the actual XML response before transformation. My OUTTAB is still empty.
*<?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:execResponse soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns1="http://webservice.hostname.com/"><execReturn xsi:type="xsd:string">*<?xml version="1.0" encoding="Shift_JIS" ?>*<Report><Header><system>
Please advise. Thank you.
Tony

Portability problem for XSL stylesheet

Hi,
I created a xsl stylesheet and a java program which just do the normal xml transformation. however, they works fine in my windows XP environment, but once i move them to my Red hat (linux) environment, they stop working... why this happening? from the exception error, the problem occurs when the stylesheet is loaded. some friends suggest that i should try to use different xslt processors, but how should i do this in the run time?
(I am currently using Xerces2.6.2 to vaildate xml file and do the transformation)
Thanks for any help

You should look at the stacktrace from the exception and fix your problem based on what you see there.
Or you could post it here so we don't have to guess...

SOAP Response XSLT Transformation Error

I am doing a webservice call and trying to transform the SOAP Response using XSLT.
I am getting the following error when the command CALL TRANSFORMATION Executes.
The element abap was expected for the XML-ABAP transformation
Please let me know if anyone ave received this error before and how did you solve it.
Regards
Sudhir Atluru

Hi Petra
for this Error com.sap.aii.af.ra.ms.api.ConfigException
check this Link
experts needed! com.sap.aii.af.ra.ms.api.ConfigException
http://help.sap.com/saphelp_nw04s/helpdata/en/78/20244134a56532e10000000a1550b0/frameset.htm
also refer SAP Note 978606
Regards
Abhishek

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:
<i>perm.unmarshal((SOAPElementImpl) result, container);</i>
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?

WebService SOAP response problems

hey,
I'm developing a WebService, using EJB's. I have a session bean, which has several methods. One of them returns, say, a class like follows:
class TeamDTO implements Serializable {
private String name;
private Integer teamId;
//getters and setters ..
I have several such methods returning various, very similar, classes. Now the problem is, when I try to test my application in the Web Services Navigator the response NEVER contains all the fields I wish. Why is that? Example of a response:
<SOAP-ENV:Envelope ...>
<SOAP-ENV:Body>
<rpl:getAllTeamsResponse ... >
   <rpl:Response ...>
    <pns:TeamDTO>
     <pns:name>team0</pns:name>
    </pns:TeamDTO>
   </rpl:Response>
</rpl:getAllTeamsResponse>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
But the TeamDTO class has apart from a name field an teamId field as well. What happened?! The same happens to other classes, but there's no rule about the missing column (first I thought it's the PK, like in the above example, but that's not the case).
What am I doing wrong? Ah, the fields are definetely not null, since in the above case it's a PK.
regards,
Kornel

Hey,
thanks for your hint, but that's not the problem here - for the example I've posted above java.lang.Integer won't appear, and for another case java.lang.String (whereas in my example String appeared). I'm sure the problem is somewhere else.. What happens if the field is null, will the appropriate tag appear in the soap response?
regards,
Kornel

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

SOAP Response XSLT mapping issue

Hi,
Source XML.
<?xml version="1.0" encoding="UTF-8"?>
<ns0:Create__CompIntfc__APC_WORKER2_CIResponse xmlns:ns0="http://peoplesoft.com/APC_WORKER2_CI">
   <ns0:notification>y</ns0:notification>
   <ns0:detail>
      <ns0:keyinformation>
         <ns0:PERSON_ID/>
         <ns0:SUBMIT_DATE/>
         <ns0:ACTION/>
      </ns0:keyinformation>
      <ns0:messages>
         <ns0:type/>
         <ns0:messagesetnumber/>
         <ns0:messagenumber/>
         <ns0:messagetext/>
         <ns0:explaintext/>
      </ns0:messages>
   </ns0:detail>
</ns0:Create__CompIntfc__APC_WORKER2_CIResponse>
Target XML
<?xml version="1.0" encoding="UTF-8"?>
<ns1:Z_HPA_357_PROVISION_USER_IMS.Response xmlns:ns1="urn:sap-com:document:sap:rfc:functions"><SUCCESS>y</SUCCESS></ns1:Z_HPA_357_PROVISION_USER_IMS.Response>
XSLT Mapping
<?xml version="1.0" encoding="utf-8"?>
<xsl:stylesheet version="2.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:fn="http://www.w3.org/2005/xpath-functions" xmlns:ns1="http://authserv.apc.com/peoplesoft">
<xsl:output method="xml" version="1.0" encoding="UTF-8" indent="yes" />
<xsl:template match="/">
    <ns1:Z_HPA_357_PROVISION_USER_IMS.Response xmlns:ns1="urn:sap-com:document:sap:rfc:functions">
      <SUCCESS>
        <xsl:value-of select="soap:Create__CompIntfc__APC_WORKER2_CIResponse/a:notification" />
      </SUCCESS>
    </ns1:Z_HPA_357_PROVISION_USER_IMS.Response>
</xsl:template>
</xsl:stylesheet>
Can somebody help to figure out the issue in higlighted area of XSLT mapping.
We just need to move "notification" value to "SUCCESS" value of RFC.
thanks.
santosh,.

Hi Santosh,
add the source namespace with a prefix:
xmlns:ns0="http://peoplesoft.com/APC_WORKER2_CI"
do it most simple generic without path
do not forget the prefix
ns0:
use xsl:value-of:
xsl:value-of select="//ns0:notification"
Regards,
Udo

XSL Stylesheet syntax

In .xsl file,
<xsl:stylesheet xmlns:xsl="http://www.w3.org/TR/WD-xsl">
What is this xmlns:xsl="http://www.w3.org/TR/WD-xsl" for?
and what is the different between xmlns:xsl="http://www.w3.org/1999/XSL/Transform ?
Any help will be grateful.
Regards,
Kelly Chen
null

Thanks for your response Rick and I hope it resolves Kelly's issue. But I too would like to know exactly what the difference is between the two examples Kelly provided because I have run into an issue where some code will run with the first example but not with the second and vice verse and without knowing why the parser is reporting an error it's hard to know which reference to use when:
1. Exactly what does a parser do with a namespace (or other URI) reference that causes it to treat the two examples differently?
2. Is there any documentation (or freeware source code) available that might show how namespace (and other) references are used to validate?
3. Does the parser compare the given string with a hard-coded string in the parser to see if they match? Does the parser look the URI up on the net to see if it exists? Does it do something like:
if uri = 'xmlns:xsl="http://www.w3.org/TR/WD-xsl"' then load namespace values from new.txt
else if uri = 'xmlns:xsl="http://www.w3.org/1999/XSL/Transform' then load namespace values from old.txt
Thanks again!
null

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

Similar Messages

Maybe you are looking for