JAXM: SOAP evelope format

My web service requests a soap envelope like the one below:
<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Body>
<Email xmlns="http://ivan2/Webapplication1">
<Cognome>Crosignani</Cognome>
</Email>
</soap:Body>
</soap:Envelope>
but with JAXM I send a different xml format:
<soap-env:Envelope xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/">
<soap-env:Header/>
<soap-env:Body>
<Email xmlns="http://ivan2/Webapplication1">
<Cognome>Crosignani</Cognome>
</soap-env:Body>
</soap-env:Envelope>
This difference cause that I get no answer from my web service.
Why there is this difference and why my soap envelope is not campatible
with the requested one
Thanks.
Ivan

Go to the following URL and click on the Chapter 13 tutorial. It should have some very helpful information on how to format your SOAP message.
http://java.sun.com/webservices/docs/1.2/tutorial/doc/index.html
Hope that helps.
Gabsaga

Similar Messages

SOAP-XML Format

Hi all,
I have a basic doubt regarding SOAP-XML format.
Why the message in XI is transformed as SOAP-XML instead of just XML. What is the advantage of using SOAP concept?
Thanks in advance.
Regards
Bhanu.

Hi,
Basically used for exchanging information in a decentralized, distributed environment
A Web service is a software system designed to support interoperable machine-to-machine interaction over a network. It has an interface described in a machine-processable format (specifically WSDL). Other systems interact with the Web service in a manner prescribed by its description using SOAP messages, typically conveyed using HTTP with an XML serialization in conjunction with other Web-related standards.
One typical use of SOAP attachments is
*for transporting intact, binary data
such as image files.
*For another example, your system may need to transport
XML documents to other parts of the system without the overhead of
validating them. These XML documents that do not need to conform to your
particular schema or DTD can be passed as attachments.
*By using SOAP attachments, the SOAP message body is much smaller
because it contains only a reference to the data and not the data itself.
*Using attachments can be more efficient because smaller SOAP messages are
processed more quickly than very large messages, and the translation of the
data to Java objects is reduced for attachments.
*SOAP attachments are implemented by wrapping the SOAP message and one
or more attachments in an envelope of Multipurpose Internet Mail Extensions
(MIME).
Regards,
Nutan

Problem in JAXM soap communication

Hello,
I'm sending simple message "some text here"
from soap client to server using JAXM
In the server i can access the message and show in the console
msg.writeTo(System.out);
How do i extract only the message from the soap envelop (How do i extract the message from the envelop in public SOAPMessage onMessage(SOAPMessage msg) method)?
This is my client
javax.xml.soap.Name name = envelope.createName("Text");
javax.xml.soap.SOAPBodyElement bodyElement = body.addBodyElement (name);
bodyElement.addTextNode ("Some Body text");
Thanks for your help

According to me, you should transform the result message to xml format, then use your favorite parser (e.g. SAX, DOM,...) to extract expected values.
                /* Do transform */
                TransformerFactory tFact = ransformerFactory.newInstance();
                Transformer transformer = tFact.newTransformer();
                Source src = msg.getSOAPPart().getContent();
                StringWriter sw = new StringWriter();
                StreamResult result = new StreamResult(sw);
                transformer.transform(src, result);
                DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance();
                factory.setValidating(false);
                factory.setNamespaceAware(true);
                DocumentBuilder parser = factory.newDocumentBuilder();
                InputSource inSource = new InputSource(new ByteArrayInputStream(sw.toString().getBytes()));
                Document dom = parser.parse(inSource);
                /* xml processing goes here. At this time, you have a DOM tree in the memory, write code to get values */
                .........hope this helps

SOAP message format after signing

Experts,
Can any one tell me the format of the soap message after the message is signed with certificate issued by third party?
I am getting signed soap message as follows :
- <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-6" 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">MIIE1TCCA72gAwIBAgICGyQwDQYJKoZIhvcNAQEFBQAwWjELMAkGA1UEBhMCU0ExDTALBgNVBAoTBFNBTUExGzAZBgNVBAsTElNBTUEgZVRydXN0IENlbnRlcjEfMB0GA1UEAxMWU0FNQSBTdGFnaW5nIFNoYXJlZCBDQTAeFw0wODA5MTYxMDUyNDJaFw0xMDA5MTYxMDUyMzdaMIGUMQswCQYDVQQGEwJTQTEoMCYGA1UEChMfTkNCQiAtIE5hdGlvbmFsIENvbW1lcmNpYWwgQmFuazEoMCYGA1UECxMfTkNCQiBXZWIgUmVnaXN0cmF0aW9uIEF1dGhvcml0eTELMAkGA1UECxMCSVQxJDAiBgNVBAMTG2UtZGhxLXMyMDF3ZWIuc2VjLnNlLmNvbS5zYTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEA2JDBfb/o41YV7/JOBKa0H/zCIF6Szpn5oEEPjIu63UoD2t3uKZgL0pDpKTrl8hNgSfnbePsn9te0sqmstflIUV8OYv6VCUKIL6ZsxcZliFP7LTWcN7VHa5J80zwJpuZI0lSOTmssRfTczT5wbRiJuf/z/ZUsc9VvP7hMT93Vc0CAwEAAaOCAewwggHoMIIBPAYDVR0gBIIBMzCCAS8wggErBg0rBgEEAYGHHQEBBgUBMIIBGDCB1QYIKwYBBQUHAgIwgcgagcVUaGlzIGNlcnRpZmljYXRlIGhhcyBiZWVuIGlzc3VlZCBieSBTQU1BIGVUcnVzdCBDZW50ZXIgb24gYmVoYWxmIG9mIE5hdGlvbmFsIENvbW1lcmNpYWwgQmFuayAoTkNCQikuIE5laXRoZXIgU0FNQSBub3IgTkNCQiBhY2NlcHQgYW55IGxpYWJpbGl0eSBmb3IgYW55IGNsYWltIGV4ZXB0IGFzIGV4cHJlc3NseSBwcm92aWRlZCBpbiB0aGlzIENQLjABggrBgEFBQcCARYyaHR0cDovL3d3dy5lVHJ1c3RjZW50ZXIuY29tLnNhL2RvY3Mvcm9vdGNhX2Nwcy5wZGYwMAYIKwYBBQUHAQEEJDAiMCAGCCsGAQUFBzABhhRodHRwOi8vMTAuMTMxLjEuNjo4MDALBgNVHQ8EBAMCA7gwJwYDVR0lBCAwHgYIKwYBBQUHAwQGCCsGAQUFBwMHBggrBgEFBQcDATAfBgNVHSMEGDAWgBSgYJsSh4qnwzTjhepPMHVJj9ncDAdBgNVHQ4EFgQUXWMeLP/opd8VqdnCf/xSX0/dD8wDQYJKoZIhvcNAQEFBQADggEBAJ2Pjv0V8ke9Vxe4FAOVJ7Hi67STUnad6gIIeT2wTUYwZD9dFf2g4NJnqJ2SF3Q9QKw5rBofU1SjuFw11hnQ3G3UK6Erkn7klS0/vVrAEAg55nzDhYPU3uZyVoobJmtLgNk507U7qkIL86p8tPCDlZoN23od1RG8uAP4K3TyiYgFozVA9tUIUGDDFbqOSACZ6tSrXDzHTfmA2l7zz4tizi/yX57SLjg3kIXKWfwo3nOEJm9xGL/4PyxaXQlNsd3srBrYl9/L78563ExKJ0UvnqKTjvuhRIsm3+E9eFhYAq1Wd/xBIXKPZEK8VwcrEQJqBnEi/2RL0jDULYMR8=</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-eed81bc1-2818-11de-a649-000e0cf559d1">
<wsu:Created ValueType="xsd:dateTime">2009-04-13T10:50:41Z</wsu:Created>
<wsu:Expires ValueType="xsd:dateTime">2009-04-13T10:55:41Z</wsu:Expires>
</wsu:Timestamp>
- <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-eed81bc0-2818-11de-cc6a-000e0cf559d1">
- <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>ybxqsfOoHwh8eItwlr2GgCzrN8Y=</ds:DigestValue>
</ds:Reference>
- <ds:Reference URI="#wsu-targetID-eed81bc1-2818-11de-a649-000e0cf559d1">
- <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>Kdki/tVoqS6zmkF7x8nA19QouzM=</ds:DigestValue>
</ds:Reference>
</ds:SignedInfo>
<ds:SignatureValue>a60173OR4QNYvp/0nEFjPaR2wR6glTj1FQO31YNGn0NR5XKuB2Ye3dfsfwfB6bdDEmXwvOcEfNln grH7hjoItDC1z8luCpXjs7Gy2viF4XCOdgqxC6MnFOwdZpKodrjESYTjzsNUiXcHUEntGzv4Ry8U zCEw9lLT7koAcTXk/NM=</ds:SignatureValue>
- <ds:KeyInfo>
- <wsse:SecurityTokenReference>
<wsse:Reference URI="#sap-6" />
</wsse:SecurityTokenReference>
</ds:KeyInfo>
</ds:Signature>
<wsse:BinarySecurityToken xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="sap-6" 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">MIIE1TCCA72gAwIBAgICGyQwDQYJKoZIhvcNAQEFBQAwWjELMAkGA1UEBhMCU0ExDTALBgNVBAoTBFNBTUExGzAZBgNVBAsTElNBTUEgZVRydXN0IENlbnRlcjEfMB0GA1UEAxMWU0FNQSBTdGFnaW5nIFNoYXJlZCBDQTAeFw0wODA5MTYxMDUyNDJaFw0xMDA5MTYxMDUyMzdaMIGUMQswCQYDVQQGEwJTQTEoMCYGA1UEChMfTkNCQiAtIE5hdGlvbmFsIENvbW1lcmNpYWwgQmFuazEoMCYGA1UECxMfTkNCQiBXZWIgUmVnaXN0cmF0aW9uIEF1dGhvcml0eTELMAkGA1UECxMCSVQxJDAiBgNVBAMTG2UtZGhxLXMyMDF3ZWIuc2VjLnNlLmNvbS5zYTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEA2JDBfb/o41YV7/JOBKa0H/zCIF6Szpn5oEEPjIu63UoD2t3uKZgL0pDpKTrl8hNgSfnbePsn9te0sqmstflIUV8OYv6VCUKIL6ZsxcZliFP7LTWcN7VHa5J80zwJpuZI0lSOTmssRfTczT5wbRiJuf/z/ZUsc9VvP7hMT93Vc0CAwEAAaOCAewwggHoMIIBPAYDVR0gBIIBMzCCAS8wggErBg0rBgEEAYGHHQEBBgUBMIIBGDCB1QYIKwYBBQUHAgIwgcgagcVUaGlzIGNlcnRpZmljYXRlIGhhcyBiZWVuIGlzc3VlZCBieSBTQU1BIGVUcnVzdCBDZW50ZXIgb24gYmVoYWxmIG9mIE5hdGlvbmFsIENvbW1lcmNpYWwgQmFuayAoTkNCQikuIE5laXRoZXIgU0FNQSBub3IgTkNCQiBhY2NlcHQgYW55IGxpYWJpbGl0eSBmb3IgYW55IGNsYWltIGV4ZXB0IGFzIGV4cHJlc3NseSBwcm92aWRlZCBpbiB0aGlzIENQLjABggrBgEFBQcCARYyaHR0cDovL3d3dy5lVHJ1c3RjZW50ZXIuY29tLnNhL2RvY3Mvcm9vdGNhX2Nwcy5wZGYwMAYIKwYBBQUHAQEEJDAiMCAGCCsGAQUFBzABhhRodHRwOi8vMTAuMTMxLjEuNjo4MDALBgNVHQ8EBAMCA7gwJwYDVR0lBCAwHgYIKwYBBQUHAwQGCCsGAQUFBwMHBggrBgEFBQcDATAfBgNVHSMEGDAWgBSgYJsSh4qnwzTjhepPMHVJj9ncDAdBgNVHQ4EFgQUXWMeLP/opd8VqdnCf/xSX0/dD8wDQYJKoZIhvcNAQEFBQADggEBAJ2Pjv0V8ke9Vxe4FAOVJ7Hi67STUnad6gIIeT2wTUYwZD9dFf2g4NJnqJ2SF3Q9QKw5rBofU1SjuFw11hnQ3G3UK6Erkn7klS0/vVrAEAg55nzDhYPU3uZyVoobJmtLgNk507U7qkIL86p8tPCDlZoN23od1RG8uAP4K3TyiYgFozVA9tUIUGDDFbqOSACZ6tSrXDzHTfmA2l7zz4tizi/yX57SLjg3kIXKWfwo3nOEJm9xGL/4PyxaXQlNsd3srBrYl9/L78563ExKJ0UvnqKTjvuhRIsm3+E9eFhYAq1Wd/xBIXKPZEK8VwcrEQJqBnEi/2RL0jDULYMR8=</wsse:BinarySecurityToken>
<wsse:BinarySecurityToken xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="sap-6" 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">MIIE1TCCA72gAwIBAgICGyQwDQYJKoZIhvcNAQEFBQAwWjELMAkGA1UEBhMCU0ExDTALBgNVBAoTBFNBTUExGzAZBgNVBAsTElNBTUEgZVRydXN0IENlbnRlcjEfMB0GA1UEAxMWU0FNQSBTdGFnaW5nIFNoYXJlZCBDQTAeFw0wODA5MTYxMDUyNDJaFw0xMDA5MTYxMDUyMzdaMIGUMQswCQYDVQQGEwJTQTEoMCYGA1UEChMfTkNCQiAtIE5hdGlvbmFsIENvbW1lcmNpYWwgQmFuazEoMCYGA1UECxMfTkNCQiBXZWIgUmVnaXN0cmF0aW9uIEF1dGhvcml0eTELMAkGA1UECxMCSVQxJDAiBgNVBAMTG2UtZGhxLXMyMDF3ZWIuc2VjLnNlLmNvbS5zYTCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEA2JDBfb/o41YV7/JOBKa0H/zCIF6Szpn5oEEPjIu63UoD2t3uKZgL0pDpKTrl8hNgSfnbePsn9te0sqmstflIUV8OYv6VCUKIL6ZsxcZliFP7LTWcN7VHa5J80zwJpuZI0lSOTmssRfTczT5wbRiJuf/z/ZUsc9VvP7hMT93Vc0CAwEAAaOCAewwggHoMIIBPAYDVR0gBIIBMzCCAS8wggErBg0rBgEEAYGHHQEBBgUBMIIBGDCB1QYIKwYBBQUHAgIwgcgagcVUaGlzIGNlcnRpZmljYXRlIGhhcyBiZWVuIGlzc3VlZCBieSBTQU1BIGVUcnVzdCBDZW50ZXIgb24gYmVoYWxmIG9mIE5hdGlvbmFsIENvbW1lcmNpYWwgQmFuayAoTkNCQikuIE5laXRoZXIgU0FNQSBub3IgTkNCQiBhY2NlcHQgYW55IGxpYWJpbGl0eSBmb3IgYW55IGNsYWltIGV4ZXB0IGFzIGV4cHJlc3NseSBwcm92aWRlZCBpbiB0aGlzIENQLjABggrBgEFBQcCARYyaHR0cDovL3d3dy5lVHJ1c3RjZW50ZXIuY29tLnNhL2RvY3Mvcm9vdGNhX2Nwcy5wZGYwMAYIKwYBBQUHAQEEJDAiMCAGCCsGAQUFBzABhhRodHRwOi8vMTAuMTMxLjEuNjo4MDALBgNVHQ8EBAMCA7gwJwYDVR0lBCAwHgYIKwYBBQUHAwQGCCsGAQUFBwMHBggrBgEFBQcDATAfBgNVHSMEGDAWgBSgYJsSh4qnwzTjhepPMHVJj9ncDAdBgNVHQ4EFgQUXWMeLP/opd8VqdnCf/xSX0/dD8wDQYJKoZIhvcNAQEFBQADggEBAJ2Pjv0V8ke9Vxe4FAOVJ7Hi67STUnad6gIIeT2wTUYwZD9dFf2g4NJnqJ2SF3Q9QKw5rBofU1SjuFw11hnQ3G3UK6Erkn7klS0/vVrAEAg55nzDhYPU3uZyVoobJmtLgNk507U7qkIL86p8tPCDlZoN23od1RG8uAP4K3TyiYgFozVA9tUIUGDDFbqOSACZ6tSrXDzHTfmA2l7zz4tizi/yX57SLjg3kIXKWfwo3nOEJm9xGL/4PyxaXQlNsd3srBrYl9/L78563ExKJ0UvnqKTjvuhRIsm3+E9eFhYAq1Wd/xBIXKPZEK8VwcrEQJqBnEi/2RL0jDULYMR8=</wsse:BinarySecurityToken>
</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-eed81bc0-2818-11de-cc6a-000e0cf559d1">
- <ns0:MasterData xmlns:ns0="http://s24dh043/SA2SEC/WSD/SATOSEC">
- <MasterData_Input>
<PARTNER_ID>XYZ</PARTNER_ID>
</MasterData_Input>
</ns0:MasterData>
</SOAP:Body>
</SOAP:Envelope>
In the above soap envelope tag "BinarySecurityToken" repeated thrice. So is it the standard method or I am missing any configuration. Becacuse our partner(webmethods) understands only one occurance of "BinarySecurityToken" in soap message.
Edited by: Santhosh on Apr 13, 2009 1:42 PM

Hi ,
Just a few pointers:
"Element caching should not be used at the top levels of an XML document by a generic encoder, since it is
unlikely that the full document would be repeated. With SOAP, it is typically wise to start element caching at the
third level, i.e. leave Envelope and Body alone. Of course, if the encoder has more knowledge of the messages
sent, going further up may pay off."
regards
joel

SOAP message formatting in Provider-based endpoint.

Good morning.
We have a Provider-based endpoint. Our client sends a SOAP request containing a signed node (XML signature). But our service is not validating it, because WLS formats the incoming message at some point. Something like this:
Client is sending:
<soap:Envelope ...>
<xml>
<someData id="data">
<node1> This is the data </node1>
</someData>
<ds:Signature>...
</ds:Signature>
<xml>
</soap:Envelope>
But when we log the incoming message, we see:
<soap:Envelope ...>
<xml>
<someData id="data"><node1> This is the data </node1></someData><ds:Signature>...</ds:Signature><xml></soap:Envelope>
That is, weblogic is changing the whitespace and line feeds.
¿How can we receive a message without changes?.
Thanks.

Swetank,
I would suggest you to get the data into XI with the help of SOAP adapter and map it to a RFC (if your requirements fit to standard) else to a zRFC and then get the response from RFC and send to the webservice. So make it as SOAP-XI-RFC synchrnous scenario.
Check this weblogs for some help on this scenario (but it is just exactly opposite to your scenario):
/people/shabarish.vijayakumar/blog/2006/03/23/rfc--xi--webservice--a-complete-walkthrough-part-1
/people/shabarish.vijayakumar/blog/2006/03/28/rfc--xi--webservice--a-complete-walkthrough-part-2
Regards,
---Satish

JAXM - SOAP Faults

Hi,
I have an almost working JAXM standalone client. However i have one problem, i cant seem to get SOAP Faults back from the SOAP Server (MS SOAP), instead i get a java exception as shown below. All other calls work fine, i would like to be able to retrieve the error information from the fault.
I am using the JAXM version that comes with the JWSDP.
I am wondering if anyone has JAXM working with SOAP faults?.. i dont want to have to change my implementation.
Kris
java.io.FileNotFoundException: http://TAZ//MeridioSOAP//MeridioSOAP.asp
 at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:549)
 at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:230)
 at com.sun.xml.messaging.client.p2p.HttpSOAPConnection.post(HttpSOAPConnection.java:198)
 at com.sun.xml.messaging.client.p2p.HttpSOAPConnection$PriviledgedPost.run(HttpSOAPConnection.java:105)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sun.xml.messaging.client.p2p.HttpSOAPConnection.call(HttpSOAPConnection.java:84)
 at com.kainos.edms.meridio.DMSMeridioSOAPOperations.sendSOAPMessage(DMSMeridioSOAPOperations.java:1597)
 at com.kainos.edms.meridio.DMSMeridioSOAPOperations.sendInformationRequest(DMSMeridioSOAPOperations.java:283)
 at com.kainos.edms.meridio.DMSMeridioSOAPHelper.getDocumentVersionInfo(DMSMeridioSOAPHelper.java:1073)
 at com.kainos.edms.meridio.DMSMeridioSOAPOperations.main(DMSMeridioSOAPOperations.java:735)
javax.xml.soap.SOAPException: java.security.PrivilegedActionException <<javax.xml.messaging.JAXMException: Message send failed>>
 at com.sun.xml.messaging.client.p2p.HttpSOAPConnection.call(HttpSOAPConnection.java:88)
 at com.kainos.edms.meridio.DMSMeridioSOAPOperations.sendSOAPMessage(DMSMeridioSOAPOperations.java:1597)
 at com.kainos.edms.meridio.DMSMeridioSOAPOperations.sendInformationRequest(DMSMeridioSOAPOperations.java:283)
 at com.kainos.edms.meridio.DMSMeridioSOAPHelper.getDocumentVersionInfo(DMSMeridioSOAPHelper.java:1073)
 at com.kainos.edms.meridio.DMSMeridioSOAPOperations.main(DMSMeridioSOAPOperations.java:735)
java.lang.NullPointerException
 at com.kainos.edms.meridio.DMSMeridioSOAPOperations.debugSOAPMessage(DMSMeridioSOAPOperations.java:1548)
 at com.kainos.edms.meridio.DMSMeridioSOAPOperations.sendInformationRequest(DMSMeridioSOAPOperations.java:288)
 at com.kainos.edms.meridio.DMSMeridioSOAPHelper.getDocumentVersionInfo(DMSMeridioSOAPHelper.java:1073)
 at com.kainos.edms.meridio.DMSMeridioSOAPOperations.main(DMSMeridioSOAPOperations.java:735)

It seems no one has ever had a SOAP fault and cant answer my question. Anyway more information. I have tracked the problem down to the following :
As per the SOAP Specification, a normal SOAP response returns with the HTTP Post code 200 OK, and a fault returns with the HTTP Post code 500 Internal Server Error.
The class sun.net.www.protocol.http.HttpURLConnection seems to throw an exception if the code returned isnt 200. Obvously this isnt any good for SOAP faults. Any ideas as to ways around this?
btw, i changed the version of the JDK i was using from 1.3.0 to 1.3.1_02 and the exception message changes from what i stated in my first message to the following which makes a bit more sense.
java.io.IOException: Server returned HTTP response code: 500 for URL: http://TAZ//MeridioSOAP//MeridioSOAP.asp
 at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:562)
 at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:230)
 at com.sun.xml.messaging.client.p2p.HttpSOAPConnection.post(HttpSOAPConnection.java:198)
 at com.sun.xml.messaging.client.p2p.HttpSOAPConnection$PriviledgedPost.run(HttpSOAPConnection.java:105)
 at java.security.AccessController.doPrivileged(Native Method)
 at com.sun.xml.messaging.client.p2p.HttpSOAPConnection.call(HttpSOAPConnection.java:84)
 at com.kainos.edms.meridio.DMSMeridioSOAPOperations.sendSOAPMessage(DMSMeridioSOAPOperations.java:1597)
 at com.kainos.edms.meridio.DMSMeridioSOAPOperations.sendAuthenticationRequest(DMSMeridioSOAPOperations.java:164)
 at com.kainos.edms.meridio.DMSMeridioSOAPHelper.login(DMSMeridioSOAPHelper.java:153)
 at com.kainos.edms.meridio.DMSMeridioSOAPOperations.main(DMSMeridioSOAPOperations.java:655)
javax.xml.soap.SOAPException: java.security.PrivilegedActionException <<javax.xml.messaging.JAXMException: Message send failed>>
 at com.sun.xml.messaging.client.p2p.HttpSOAPConnection.call(HttpSOAPConnection.java:88)
 at com.kainos.edms.meridio.DMSMeridioSOAPOperations.sendSOAPMessage(DMSMeridioSOAPOperations.java:1597)
 at com.kainos.edms.meridio.DMSMeridioSOAPOperations.sendAuthenticationRequest(DMSMeridioSOAPOperations.java:164)
 at com.kainos.edms.meridio.DMSMeridioSOAPHelper.login(DMSMeridioSOAPHelper.java:153)
 at com.kainos.edms.meridio.DMSMeridioSOAPOperations.main(DMSMeridioSOAPOperations.java:655)
java.lang.NullPointerException
 at com.kainos.edms.meridio.DMSMeridioSOAPOperations.debugSOAPMessage(DMSMeridioSOAPOperations.java:1548)
 at com.kainos.edms.meridio.DMSMeridioSOAPOperations.sendAuthenticationRequest(DMSMeridioSOAPOperations.java:166)
 at com.kainos.edms.meridio.DMSMeridioSOAPHelper.login(DMSMeridioSOAPHelper.java:153)
 at com.kainos.edms.meridio.DMSMeridioSOAPOperations.main(DMSMeridioSOAPOperations.java:655)
java.lang.NullPointerException
 at com.kainos.edms.meridio.DMSMeridioSOAPOperations.main(DMSMeridioSOAPOperations.java:657)

SOAP encoding formats and interoperability

Hi,
Being new to Web Services, I have spend quite a bit of time over the past few
days investigating the technology. Based on several newgroup posts and articles
I have found, it appears that for the best performance and scalability, you should
use SOAP document-style encoding [1]. My question is how do the various encoding
formats affect interoperabiliy? The article referenced below indicates that most
of the .NET tools default to using document-style encoding. Is it safe to say
for the best of all worlds (performance, scalability, and interoperability) you
should develop your Web Services using document-style encoding?
1. http://dev2dev.bea.com/products/wlworkshop/articles/Cohen.jsp
TIA,
Kent

Hi Kent,
Yes, doc/lit is the best approach for interop. Also look for guidance
from the WS-I Basic Profile [1]
Hope this helps,
Bruce
[1]
http://www.ws-i.org/Profiles/Basic/2003-08/BasicProfile-1.0a.html
Kent Kvarfordt wrote:
>
Hi,
Being new to Web Services, I have spend quite a bit of time over the past few
days investigating the technology. Based on several newgroup posts and articles
I have found, it appears that for the best performance and scalability, you should
use SOAP document-style encoding [1]. My question is how do the various encoding
formats affect interoperabiliy? The article referenced below indicates that most
of the .NET tools default to using document-style encoding. Is it safe to say
for the best of all worlds (performance, scalability, and interoperability) you
should develop your Web Services using document-style encoding?
1. http://dev2dev.bea.com/products/wlworkshop/articles/Cohen.jsp
TIA,
Kent

Coffee Break - JAXM/SOAP - 404 Not Found

In the Coffee Break application, we have one component for SOAP/JAXM. Its a servlet that handles request and sends appropriate response. I want to deploy only this component, and will use TestOrderRequest/TestPriceListRequest to access this service. I deploy the war file containing relevant class files and a web.xml to WAS. And when I run the test client, I get a 404 Not Found. Whats wrong with this?

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN" "http://java.sun.com/dtd/web-app_2_3.dtd">
<web-app id="WebApp_ID">
<servlet id="Servlet_1062757313735">
<servlet-name>com.sun.cb.PriceListServlet</servlet-name>
<servlet-class>com.sun.cb.PriceListServlet</servlet-class>
<load-on-startup>1</load-on-startup>
</servlet>
<servlet id="Servlet_1062775215094">
<servlet-name>com.sun.cb.ConfirmationServlet</servlet-name>
<servlet-class>com.sun.cb.ConfirmationServlet</servlet-class>
<load-on-startup>1</load-on-startup>
</servlet>
<servlet-mapping id="ServletMapping_1062757313751">
<servlet-name>com.sun.cb.PriceListServlet</servlet-name>
<url-pattern>/getPriceList</url-pattern>
</servlet-mapping>
<servlet-mapping id="ServletMapping_1062775215094">
<servlet-name>com.sun.cb.ConfirmationServlet</servlet-name>
<url-pattern>/orderCoffee</url-pattern>
</servlet-mapping>
<session-config id="SessionConfig_1062757313750">
<session-timeout>60</session-timeout>
</session-config>
</web-app>
and the url am trying is
http://localhost:8080/jaxm-coffee-supplier/orderCoffee
note that a jsp kept in the same application is accessible from browser

SOAP envelope format

Hi,
I must make sample code of web service calls for PHP and Java to our clients. So far I have got it working with PHP but I have trouble to successfuly call web service in Java.
I have generated stub files with wscompile -keep -gen:client config.xml
It makes SOAP envelope, and calls service but there is no response - unfortunetly i cant debug cause from server side, but it must have something to do with SOAP envelope. Server side is done with Microsoft SOAP Toolkit. I have included Java generated envelope and nosoap (PHP)generated envelope (PHP one works). (PS! TimeToSend field is 0 in PHP version and 0.0 in Java, can it be cause?)
Envelope with Java:
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:enc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:ns0="http://tempuri.org/fmts/message/" env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
<env:Body>
<ns0:SendSMS>
<MessageText xsi:type="xsd:string">test</MessageText>
<TimeToSend xsi:type="xsd:double">0.0</TimeToSend>
<StatusURL xsi:type="xsd:string"></StatusURL>
</ns0:SendSMS>
</env:Body>
</env:Envelope>
Using nosoap lib for PHP envelope looks like this:
<SOAP-ENV:Envelope SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:si="http://soapinterop.org/xsd" xmlns:nu="http://tempuri.org/fmts/message/">
<SOAP-ENV:Body>
<nu:SendSMS>
<MessageText xsi:type="xsd:string">PHP</MessageText>
<TimeToSend xsi:type="xsd:double">0</TimeToSend>
<StatusURL xsi:type="xsd:string"></StatusURL>
</nu:SendSMS>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>

Found out what was frong. There was password field in envelope (removed it in previous post - and i managed to enter wrong password)

How can I get JAXM SOAP with Attachement parts?

I received a SOAP with attachment message.
Attached data is XML document("text/xml" type).
But when I try to get a attachment part by using below source code, I got a NullPointerException.
Iterator it = message.getAttachments();
AttachmentPart attachment = (AttachmentPart)it.next();
StreamSource content = (StreamSource)attachment.getContent(); <=content is not Null.
InputStream inputstream = content.getInputStream(); <= inputstream is Null.
StreamSource object is OK, but it doesn't return InputStream object.
Does anyone know what the problem is?
Thanks in advance.
Junhong.

Hi!
Use the following to get the stream:
InputStream is = attachment.getDataHandler().getInputStream();

Google WebService SOAP Help

Hello,
has anybody been able to get the Google WebService example working (access to external services) in EP6?
I get weird errors from PROXY settings or XML response format exceptions depending on proxy settings.
I have no need for proxy but direct connection and can perfectly read a Google URL from within my component.
Environment is EP6 SP2 Patch 3 + Eclipse 2.1.3.
I am also facing a problem with NetWeaver Developer Studio 2.0.5 not generating soap proxies correctly (it adds method calls to retrieve cookies from the soap response; these methods are not implemented in the interface).
I have developed my own soap service on an EP6 and a client running on another EP6 and this works perfectly. Still no way to access Google.
Obviously I have my own account key in google to access the api and I can make it work outside EP6.
Something to do with http chunking?
PLEASE HELP !

Exception
com.inqmy.lib.xml.parser.ParserException: XMLParser: No data allowed here:51a (:main:, row:1, col:3)
 at com.inqmy.lib.xml.parser.XMLParser.scanProlog(XMLParser.java:2467)
 at com.inqmy.lib.xml.parser.XMLParser.scanDocument(XMLParser.java:2505)
 at com.inqmy.lib.xml.parser.XMLParser.parse0(XMLParser.java:151)
 at com.inqmy.lib.xml.parser.AbstractXMLParser.parseAndCatchException(AbstractXMLParser.java:110)
 at com.inqmy.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:127)
 at com.inqmy.lib.xml.parser.AbstractXMLParser.parse(AbstractXMLParser.java:195)
 at com.inqmy.lib.xml.parser.DOMParser.parse(DOMParser.java:90)
 at com.inqmy.lib.xml.parser.DOMParser.parse(DOMParser.java:142)
 at com.inqmy.lib.jaxm.soap.SOAPPartImpl.parseDocument(SOAPPartImpl.java:60)
 at com.inqmy.lib.jaxm.soap.SOAPPartImpl.setContent(SOAPPartImpl.java:220)
 at com.inqmy.lib.jaxm.soap.SOAPMessageImpl.<init>(SOAPMessageImpl.java:76)
 at com.inqmy.lib.jaxm.soap.MessageFactoryImpl.createMessage(MessageFactoryImpl.java:40)
 at com.inqmy.lib.jaxm.soap.SOAPConnectionImpl.call(SOAPConnectionImpl.java:160)
 at com.sapportals.portal.prt.service.soap.SOAPService.call(SOAPService.java:149)
 at com.sapportals.portal.prt.service.soap.PRTSOAPCall.invokeMethod(PRTSOAPCall.java:209)
 at com.whr.google.client.GoogleSearch.doGoogleSearch(GoogleSearch.java:321)
 at com.whr.google.client.Google.doContent(Google.java:49)
 at .............

PI 7.0 SOAP message reply HTTP 500 and after the fault message

Hello Everybody,
I have the scenario RFC -> XI -> SOAP in synchronous mode.
I use for the mapping XSLT because I have to put some dynamic data comming from the RFC in the header of envelope.
At level of adapter receiver SOAP , I flag the "do not use envelop"
In normal, that works .
When the is an fonctionnal error in SOAP service, it sends me back an error HTTP 500 and afterwards the fault message in a soap envelop format. In that case, how can I pass over this error to treat the envelop because in adapter, it is stopped and it returns a short dump to the RFC.
Is there somebody who can help me with this problem ?
Thanks in adavance for your answers .
Regards.
Eric.

Hi,
In case of a SOAP error while processing the request, the SOAP HTTP server MUST issue an HTTP 500 "Internal Server Error" response and include a SOAP message in the response containing a SOAP Fault element
Thanks,
RamuV

Soap Fault mapping issue

Hi,
I have a synchronous scenario of (request) Proxy --> XI --> SOAP and (response) SOAP --> XI --> Proxy. I am having an issue returning the application soap faults back to the sender system. When I enter invalid data while testing this webservice call with a soap client directly without XI I get a soap fault response:
<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>
 <soapenv:Fault>
 <faultcode>soapenv:Server.generalException</faultcode>
 <faultstring>Login failed</faultstring>
 <detail>
 <LoginFault xmlns="NAMESPACE">
 <exceptionCode>710</exceptionCode>
 <exceptionMessage>Login failed</exceptionMessage>
 </LoginFault>
 <ns1:exceptionName xmlns:ns1="http://xml.apache.org/axis/">NAMESPACE</ns1:exceptionName>
 </detail>
 </soapenv:Fault>
 </soapenv:Body>
</soapenv:Envelope>
When testing this through XI, the response message after the Soap call is returning the following soap fault in XI payload:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

<LoginFault xmlns="NAMESPACE">
<exceptionCode>710</exceptionCode>
<exceptionMessage>Login failed</exceptionMessage>
</LoginFault>
Notice just the detail body exists in the payload instead of the soap evelope and body, which I read is stripped off within XI in the case of application errors. I have setup a fault message mapping to tie the wsdl login fault with the standard fault message type and included this in the service interfaces and operations mapping. When the soap fault happens within XI I am getting the following mapping error:
NO_MAPPINGPROGRAM_FOUND: Mapping program is not available in runtime cache:
I am expecting the fault mapping to be executed in this case but doesn't seem to be found. Any ideas why this mapping error is occuring and not being directed to my fault message mapping? Is the mapping expecting the soap envelope and body to be included in the payload?
Any suggestions would be appreciated.
Thanks,
Nate

Here are the errors I am seeing within the sxmb_moni transaction:
Call adapter exception:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>XIServer</SAP:Category>
<SAP:Code area="MAPPING">NO_MAPPINGPROGRAM_FOUND</SAP:Code>
<SAP:P1>Object ID 35F8008AA0A830FC93FC221572A15ABD Software Component DC6FB8300EDE11DC8E05DB6DA3E77028</SAP:P1>
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:Stack>Mapping program is not available in runtime cache: Object ID 35F8008AA0A830FC93FC221572A15ABD Software Component DC6FB8300EDE11DC8E05DB6DA3E77028</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Response Message Error:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1">
<SAP:Category>Application</SAP:Category>
<SAP:Code area="UNKNOWN">APPLICATION_ERROR</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText>application fault</SAP:AdditionalText>
<SAP:ApplicationFaultMessage namespace="NAMESPACE REMOVED">LoginFault</SAP:ApplicationFaultMessage>
<SAP:Stack />
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
and response message payload:
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <LoginFault xmlns="NAMESPACE REMOVED">
<exceptionCode>710</exceptionCode>
<exceptionMessage>Login failed</exceptionMessage>
</LoginFault>

WSSE problems with soap envelope

Hi,
I'm trying to use a Java control to talk to an external website which
requires a digital signature in the Soap Header and cannot seem to get a
properly formatted soap message.
Based on the documentation, I have set up the wsse file to specify that I
want to add a digital signature and also specify my alias, password,
keystore, and keystorepassword. I am sure that it is picking up the digital
cert and is able to take out the private key and all (I get exceptions if I
move the cert or if I specify an incorrect password).
I am also using my own ClientHandler to add in additional Header elements
that are required by the destination webservice. I know that that is being
properly based on inspecting the soap message in my header and that the
external webservice is able to process my request. In adding in the WSSE
Client Handler however, it looks like the security handler is adding an
additional Header element rather than adding the required subelements into
the existing Header element (the one that my Client Handler already
created). I am getting back an exception from the webservice saying that
the Header element is already defined.
Is it possible that the WSSEClientHandler, while adding the necessary
attributes is not looking for or detecting the already existing Header?
I have submitted a case to weblogic support but have not yet heard back
(case # 525549).
Thanks,
Gary

Hi Klaus
In your wsdl file the soap address tag (given below)
<soap:address location="http://xxxxxxxx:8000/XISOAPAdapter/MessageServlet?channel=:Foo_SOAP_Service:SOAP_Foo_out&version=3.0&Sender.Service=Foo_SOAP_Service&Interface=urn%3A%2F%2Fporeceive.xi.pse.siemens.com%5Efoo_out_sync" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"/>
is to be edited as
<soap:address location="http://xxxxxxxx:50000//XISOAPAdapter/MessageServlet?channel=:Foo_SOAP_Service:SOAP_Foo_out" />
because the soap address format should be like :
http://host:port/XISOAPAdapter/MessageServlet?channel=party:service:channel
For more information :
http://help.sap.com/saphelp_nw04/helpdata/en/0d/5ab43b274a960de10000000a114084/frameset.htm
Hope this will be helpful.
Regards
Suraj

Authentication in Sender SOAP Adapter

Hi experts,
We have a scenario were EP sends SOAP Message to XI. We have created the WSDL from XI and it has been consumed by EP. When EP tries to send the SOAP Request to XI we get UnAuthorized Exception.
Below is the Exception
#1.5#001372E937FC00670000012000000D8C0004298100849F8B#1171533943519#com.sap.portal.portal#sap.com/irj#com.sap.portal.portal#CLASP#6953####18f1d310bcdc11db9500001372e937fc#SAPEngine_Application_Thread[impl:3]_29##0#0#Warning#1#/System/Server#Java###Call failed
[EXCEPTION]
#1#com.sap.engine.services.webservices.jaxm.soap.accessor.NestedSOAPException: Problem in server response: [Unauthorized].
     at com.sap.engine.services.webservices.jaxm.soap.SOAPConnectionImpl.call(SOAPConnectionImpl.java:207)
     at com.sap.engine.services.webservices.jaxm.soap.SOAPConnectionImpl.call(SOAPConnectionImpl.java:163)
     at com.sap.engine.services.webservices.jaxm.soap.SOAPConnectionImpl.call(SOAPConnectionImpl.java:325)
     at com.sapportals.portal.prt.service.soap.SOAPService.call(SOAPService.java:152)
     at com.sapportals.portal.prt.service.soap.PRTSOAPCall.invokeMethod(PRTSOAPCall.java:209)
     at service.XIUserCreateCall.IOS_UserCreate(XIUserCreateCall.java:168)
     at service.XIUserComp.doContent(XIUserComp.java:46)
I tried to send the basic authentication details in my URL. But it didn't work.
Pl. help me resolve this.

HI,
for XI EP
Please see the below links so that you can have clear Idea..
/people/saravanakumar.kuppusamy2/blog/2005/02/07/interfacing-to-xi-from-webdynpro
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/webas/java/integrating%20web%20dynpro%20and%20sap%20xi%20using%20jaxb%20part%20ii.article
Consuming XI Web Services using Web Dynpro Part II-/people/riyaz.sayyad/blog/2006/05/08/consuming-xi-web-services-using-web-dynpro-150-part-ii
Consuming XI Web Services using Web Dynpro Part I -/people/riyaz.sayyad/blog/2006/05/07/consuming-xi-web-services-using-web-dynpro-150-part-i
/people/sap.user72/blog/2005/09/15/creating-a-web-service-and-consuming-it-in-web-dynpro
/people/sap.user72/blog/2005/09/15/connecting-to-xi-server-from-web-dynpro
Regards
Chilla..

JAXM: SOAP evelope format

Similar Messages

Maybe you are looking for