Find Soap Message Output Format

Hi,
I am trying to send message with receiver soap adapter to the client but the message i have in sxmb_moni is different than the one the client receives. I found this weblog that could help finding the message that is going out of the adapter : /people/varadharajan.krishnasamy/blog/2007/01/09/troubleshooting-soap-message--xi but when i open the application enter values and click on add nothing happens.
Have someone already done this or knows how to see the output soap message?
Best regards,
Laurent.

Hi Laurent,
Use Messaging System servlet..
http://<host_XI>:<port>/MessagingSystem (case sensitive)
Find your message, click Message Details (eye icon) , then Display Message Bytes
Peter

Similar Messages

Outputting SOAP Message to Browser In JSP

I am using SAAJ to create a soap message and sending it to a web service. It will then receive a response int eh form of a SOAP message (XML). I would like to be able to output this message to the browser window. I am able to output to the System.out using the SAAJ writeTo() method, but cannot seemt o find a way to output this to the window from a JSP page. Any suggestions?
Thanks!

Why not justwriteTo(response)?

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

Printing formatted Soap Message in conole

Hello,
I have written one service and one SOAPMessageHandler, in this class i need to print formatted soap message,but how i dont know
here is my code:
                                SOAPMessage soapMessage = context.getMessage();
                    SOAPEnvelope soapEnv = soapMessage.getSOAPPart().getEnvelope();
                    SOAPHeader soapHeader = soapEnv.getHeader();
                    if (soapHeader == null) {
                         System.out.println(" Adding Empty Header [" + this.getClass().getSimpleName() + "]");
                         soapHeader = soapEnv.addHeader();
                    QName qIdName =.....
                    SOAPHeaderElement soapHeaderElem = soapHeader.addHeaderElement(qIdName);
                    soapHeaderElem.setActor(SOAPConstants.URI_SOAP_ACTOR_NEXT);
                    soapHeaderElem.addTextNode("some id name");
                    soapMessage.writeTo(System.out);Can anyone tell me how to do that? is there some parameter set needed (As it is JAXB_FORMATTED_OUTPUT )?

Hi,
Can you try using ByteArrayOutputStream to print soap message
here is the snippet of code
=================
SOAPMessage soapMessage = messageContext.getMessage()
dumpSOAPMessage(soapMessage);
============================
private void dumpSOAPMessage(SOAPMessage msg) {
if (msg == null) {
System.out.println("SOAP Message is null");
return;
System.out.println("");
System.out.println("--------------------");
System.out.println("DUMP OF SOAP MESSAGE");
System.out.println("--------------------");
try {
ByteArrayOutputStream baos = new ByteArrayOutputStream();
msg.writeTo(baos);
System.out.println(baos.toString(getMessageEncoding(msg)));
// show included values
String values = msg.getSOAPBody().getTextContent();
System.out.println("Included values:" + values);
} catch (Exception e) {
e.printStackTrace();
Hope that helps
Regards,
sunil

Formating WSDL SOAP message using external .xsd file

Hi,
I am trying to build web service from java method using xml schema in .xsd file to format soap messages. How can I do this? What steps should I take to accomplish this?
When I tried to do this using wizard for building web service, and map custom java classes to xml schema types , I got generator error: java.util.NoSuchElementException.
When I managed to generate web service using that custom mappings (without generator error) , I couldn't deploy that service on server. At deploy time i alway get compile error without named source where error is....

hI,
How to add the the below soap frame thru XSLT mapping.
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:eb="http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd">
<SOAP-ENV:Header>
<eb:MessageHeader xmlns:eb="http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd" SOAP-ENV:mustUnderstand="1" eb:version="2.0">
<eb:From>
<eb:PartyId>0037123456678</eb:PartyId>
<eb:Role>Sender</eb:Role>
</eb:From>
<eb:From>
<eb:PartyId>NDEAFIHH</eb:PartyId>
<eb:Role>Intermediator</eb:Role>
</eb:From>
<eb:To>
<eb:PartyId>FI2757800750155448</eb:PartyId>
<eb:Role>Receiver</eb:Role>
</eb:To>
<eb:To>
<eb:PartyId>OKOYFIHH</eb:PartyId>
<eb:Role>Intermediator</eb:Role>
</eb:To>
<eb:CPAId>yoursandmycpa</eb:CPAId>
<eb:ConversationId/>
<eb:Service>Routing</eb:Service>
<eb:Action>ProcessInvoice</eb:Action>
<eb:MessageData>
<eb:MessageId>20081228-010142</eb:MessageId>
<eb:Timestamp>2008-12-28T01:01:42+03:00</eb:Timestamp>
<eb:RefToMessageId/>
<eb:RefToMessageId>XS1027.LPTF82/268</eb:RefToMessageId>
</eb:MessageData>
</eb:MessageHeader>
</SOAP-ENV:Header>
<SOAP-ENV:Body>
<eb:Manifest eb:id="Manifest" eb:version="2.0">
<eb:Reference eb:id="Finvoice" xlink:href="XS1027.LPTF82/268">
<eb:Schema eb:location=" http://www.finvoice.info/yrityksen_verkkolasku/ladattavat/Tekniset tiedostot/schemat/Finvoice.xsd" eb:version="2.0"/>
</eb:Reference>
</eb:Manifest>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
<?xml version="1.0" encoding="ISO-8859-15"?>
<!DOCTYPE Finvoice SYSTEM "Finvoice.dtd">
<?xml-stylesheet type="text/xsl" href="Finvoice.xsl"?>
Thanks and Regards,
Hymavathi

SOAP Messaging Using Crystal Reports Web Services To Return Report in PDF or Excel Format

All,
I am trying to use SOAP messaging to fetch a Crystal Report through a Managed repository and getting back either a PDF or Excel file. For some reason, any reference to web services on this site I cannot access. Like thread, "Using Web Services on the Crystal Report Server XI to return reports". Can anyone point in a direction to Web Service Calls API documentation or does this not exist ?????? I would hope this product has this capability.
Thanks In Advance,
Tom

XI Release 2 Service Pack 2 introduced the Business Process BI Web Services, that allow you to retrieve reports using SOAP messaging.
It's documented here:
http://devlibrary.businessobjects.com/BusinessObjectsXIR2SP2/en/en/WS_SDK/wssdk_portal/doc/wssdk_bpbi_doc.pdf
Sincerely,
Ted Ueda

WLS 7.0 sp2 - Servlet Problems with SOAP messages

          I'm using Weblogic 7.0 SP2 and trying to create a Servlet to receive SOAP wrapped
          XML messages. I'm getting the following error. Is this a problem with WLS7.0sp2's
          support of JAXM? The System.out.println's indicate I have successfully received
          the incoming SOAP request and then successfully formatted the SOAP response, but
          upon returning saving the response it appears to blow up. Does anyone have any
          suggestions?
          I need to do the following in a servlet:
          - receive an incoming SOAP request with an embedded XML message
          - perform some processing
          - return a SOAP response with an embedded XML message
          Should I be using JAXM? Or can I do this same task easily with JAX-RPC?
          <Feb 24, 2004 4:10:42 PM AST> <Error> <HTTP> <101017> <[ServletContext(id=260434
          7,name=isd.war,context-path=)] Root cause of ServletException
          java.lang.Error: NYI
          at weblogic.webservice.core.soap.SOAPMessageImpl.saveRequired(SOAPMessag
          eImpl.java:360)
          at javax.xml.messaging.JAXMServlet.doPost(Unknown Source)
          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:1058)
          at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
          pl.java:401)
          at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
          pl.java:306)
          at weblogic.servlet.internal.WebAppServletContext$ServletInvocationActio
          n.run(WebAppServletContext.java:5445)
          at weblogic.security.service.SecurityServiceManager.runAs(SecurityServic
          eManager.java:780)
          at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppSe
          rvletContext.java:3105)
          at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestIm
          pl.java:2588)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:213)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:189)
          >
          I've stripped the code down so that all it does is verifies the incoming SOAP/XML
          request and creates a hard-coded response... be gentle... I'm a novice at this
          import javax.xml.soap.*;
          import javax.servlet.*;
          import javax.servlet.http.*;
          // import javax.xml.transform.*;
          import java.util.*;
          import java.io.*;
          public class RegisterServlet extends HttpServlet
          static MessageFactory fac = null;
          static
          try
          fac = MessageFactory.newInstance();
          catch (Exception ex)
          ex.printStackTrace();
          public void init(ServletConfig servletConfig) throws ServletException
          super.init(servletConfig);
          public void doPost(HttpServletRequest req, HttpServletResponse resp) throws ServletException,
          IOException
          try
          System.out.println("** Note: doPost() Entering req = " + req);
          // Get all the headers from the HTTP request
          MimeHeaders headers = getHeaders(req);
          // Get the body of the HTTP request
          InputStream is = req.getInputStream();
          // Now internalize the contents of a HTTP request
          // and create a SOAPMessage
          SOAPMessage msg = fac.createMessage(headers, is);
          System.out.println("** Note: doPost() Step A");
          SOAPMessage reply = null;
          reply = onMessage(msg);
          System.out.println("** Note: doPost() Step B reply = " + reply);
          if (reply != null)
          * Need to call saveChanges because we're
          * going to use the MimeHeaders to set HTTP
          * response information. These MimeHeaders
          * are generated as part of the save.
          if (reply.saveRequired())
          System.out.println("** Note: doPost() Step C reply.saveRequired()");
          reply.saveChanges();
          resp.setStatus(HttpServletResponse.SC_OK);
          putHeaders(reply.getMimeHeaders(), resp);
          // Write out the message on the response stream
          OutputStream os = resp.getOutputStream();
          System.out.println("** Note: doPost() Step D os = " + os);
          reply.writeTo(os);
          os.flush();
          else
          resp.setStatus(HttpServletResponse.SC_NO_CONTENT);
          catch (Exception ex)
          throw new ServletException("** Error: SAAJ POST failed: " + ex.getMessage());
          static MimeHeaders getHeaders(HttpServletRequest req)
          Enumeration enum = req.getHeaderNames();
          MimeHeaders headers = new MimeHeaders();
          while (enum.hasMoreElements())
          String headerName = (String)enum.nextElement();
          String headerValue = req.getHeader(headerName);
          StringTokenizer values =
          new StringTokenizer(headerValue, ",");
          while (values.hasMoreTokens())
          headers.addHeader(headerName,
          values.nextToken().trim());
          return headers;
          static void putHeaders(MimeHeaders headers, HttpServletResponse res)
          Iterator it = headers.getAllHeaders();
          while (it.hasNext())
          MimeHeader header = (MimeHeader)it.next();
          String[] values = headers.getHeader(header.getName());
          if (values.length == 1)
          res.setHeader(header.getName(),
          header.getValue());
          else
          StringBuffer concat = new StringBuffer();
          int i = 0;
          while (i < values.length)
          if (i != 0)
          concat.append(',');
          concat.append(values[i++]);
          res.setHeader(header.getName(), concat.toString());
          // This is the application code for handling the message.
          public SOAPMessage onMessage(SOAPMessage message)
          SOAPMessage replymsg = null;
          try
          System.out.println("** Note: OnMessage() Entering msg = " + message);
          //Extract the ComputerPart element from request message and add to reply SOAP
          message.
          SOAPEnvelope reqse = message.getSOAPPart().getEnvelope();
          SOAPBody reqsb = reqse.getBody();
          //System.out.println("** Note: OnMessage() Step B");
          System.out.println("** Note: OnMessage () Step A Soap Request Message Body = "
          + reqsb);
          //Create a reply mesage from the msgFactory of JAXMServlet
          System.out.println("** Note: OnMessage () Step B");
          replymsg = fac.createMessage();
          SOAPPart sp = replymsg.getSOAPPart();
          SOAPEnvelope se = sp.getEnvelope();
          SOAPBody sb = se.getBody();
          System.out.println("** Note: OnMessage () Step C Soap Reply Before Message Body
          = " + sb);
          se.getBody().addBodyElement(se.createName("RegisterResponse")).addChildElement(se.createName("ErrorCode")).addTextNode("000");
          System.out.println("** Note: OnMessage () Step D Soap Reply After Message Body
          = " + sb);
          replymsg.saveChanges();
          System.out.println("** Note: OnMessage() Exiting replymsg = " + (replymsg));
          catch (Exception ex)
          ex.printStackTrace();
          return replymsg;


Michael,
I got the same error on WLS8.1/Win2K professional and apache FOP (old version).
After digging into the WLS code and FOP(old version). i found the conflict happens
on
the "org.xml.sax.parser" system property. In WLS code, they hard coded like the
following when startup weblogic server:
System.setProperty("org.xml.sax.parser", "weblogic.xml.jaxp.RegistryParser");
But the FOP code try to use the "org.xml.sax.parser" system property to find the
sax parser then conlict happens.
Here is the response from BEA support :
"I consulted with our developers regarding the question of whether we can change
the hard-coded value for the java system property: org.xml.sax.parser by using
a configuration parameter and I found that unfortunately there is no specific
setting to change the value. As you had mentioned in your note the org.xml.sax.parser
system property can be changed programmatically in your application code."
I solve my problem by using newer apache FOP (it never use the system property:org.xml.sax.parser
any more) and XML Registy for WLS8.1.
Good luck.
David Liu
Point2 Technologies Inc.
"p_michael" <[email protected]> wrote:
>
Help.
When we migrated from WLS 6.1 to WLS 7.0 SP2 when encountered a problem
with XML
parsing that did not previously exist.
We get the error "weblogic.xml.jaxp.RegistryParser is not a SAX driver".
What does this mean? And, what should we do about it.
p_michael

SOAP Message

Hi,
I'm new to Java Web Services. I tried to create a soap mesg. but unable to connect to server, where the service is running.
Here is the piece of code.
MessageFactory msgFactory = MessageFactory.newInstance();
SOAPMessage mesg = msgFactory.createMessage();
mesg.setProperty(SOAPMessage.WRITE_XML_DECLARATION, "true");
mesg.setProperty(SOAPMessage.CHARACTER_SET_ENCODING, "utf-8");
SOAPEnvelope envelope = mesg.getSOAPPart().getEnvelope();
envelope.setAttribute("xmlns:xsd","http://www.w3.org/2001/XMLSchema");
envelope.setAttribute("xmlns:xsi","http://www.w3.org/2001/XMLSchema-instance");
envelope.setAttribute("soap:encodingStyle","http://schemas.xmlsoap.org/soap/encoding");
String url = "http://192.168.4.214/dmwebservice/service1.asmx";
SOAPBody body = envelope.getBody();
SOAPFactory soapFactory = SOAPFactory.newInstance();
Name bodyName = soapFactory.createName("setBinaryData","xmlns", "http://tempuri.org/");
SOAPBodyElement bodyElement = body.addBodyElement(bodyName);
SOAPConnectionFactory factory = SOAPConnectionFactory.newInstance();
SOAPConnection con = factory.createConnection();
String url = "http://192.168.4.214/dmwebservice/service1.asmx";
mesg.writeTo(System.out);
//SOAPMessage response = con.call(mesg, new URL(url));
SOAPMessage response = con.call(mesg, url);
response.writeTo(System.out);
con.close();
i'm calling the service method "setBinaryData" and the service is running at "http://192.168.4.214/dmwebservice/service1.asmx"
please find the request and response of above sample. The server is not recognizing the HTTP Header SOAPAction. Can you please let me know how to set the "HTTP Header SOAPAction"?
[java] **** request ****
[java] <?xml version="1.0" encoding="utf-8"?>
[java] <SOAP-ENV:Envelope soap:encodingStyle="http://schemas.xmlsoap.org/so
ap/encoding" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xs
d="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema
-instance"><SOAP-ENV:Header/><SOAP-ENV:Body><xmlns:setBinaryData xmlns:xmlns="ht
tp://tempuri.org/"/></SOAP-ENV:Body></SOAP-ENV:Envelope>
[java] **** response ****
[java] <?xml version="1.0" encoding="utf-8"?>
[java] <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">
[java] <soap:Body>
[java] <soap:Fault>
[java] <faultcode>soap:Client</faultcode>
[java] <faultstring>System.Web.Services.Protocols.SoapException: Serv
er did not recognize the value of HTTP Header SOAPAction: .
[java] at System.Web.Services.Protocols.Soap11ServerProtocolHelper.Route
Request()
[java] at System.Web.Services.Protocols.SoapServerProtocol.Initialize()
[java] at System.Web.Services.Protocols.ServerProtocol.SetContext(Type t
ype, HttpContext context, HttpRequest request, HttpResponse response)
[java] at System.Web.Services.Protocols.ServerProtocolFactory.Create(Typ
e type, HttpContext context, HttpRequest request, HttpResponse response, Boolean
& abortProcessing)</faultstring>
[java] <detail />
[java] </soap:Fault>
[java] </soap:Body>
Thanks in Advance.
Subhani.

Hi,
Perhaps you can help.
I've got a problem related to usage of SOAP in Java. I receive a file containing SOAP message with XML attachment. I store it on hard disk.
Then I create a SOAP message as it is shown in source code below.
When I try to get the attachment, the method doesn't return anything (the number of attachments is 0).
If I pass to method createMessage value null instead of new MimeHeaders(), the result is the same.
What can be the problem? How to solve it? Any idea?
Looking forward any support.
BR,
rafikoko
MessageFactory factory = MessageFactory.newInstance();
SOAPMessage message = factory.createMessage(new MimeHeaders(), new FileInputStream(xmlFile));
Iterator attachments = message.getAttachments();
log4j.error("TEST:before while:"+message.countAttachments());
while(attachments.hasNext()){
log4j.error("TEST:while");
Object finvoice = attachments.next();
log4j.error("TEST:Finvoice:"+finvoice);
}Below is my example soap message:
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:eb="http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd">
<SOAP-ENV:Header>
<eb:MessageHeader xmlns:eb="http://www.oasis-open.org/committees/ebxml-msg/schema/msg-header-2_0.xsd"
SOAP-ENV:mustUnderstand="1" eb:id="20030222133003285">
    <eb:From>
       <eb:PartyId>FI9859292720000267</eb:PartyId>
       <eb:Role>Sender</eb:Role>
    </eb:From>
    <eb:From>
       <eb:PartyId>OKOYFIHH</eb:PartyId>
       <eb:Role>Intermediator</eb:Role>
    </eb:From>
    <eb:To>
       <eb:PartyId>FI3329501800008512</eb:PartyId>
       <eb:Role>Receiver</eb:Role>
    </eb:To>
    <eb:To>
       <eb:PartyId>NDEAFIHH</eb:PartyId>
       <eb:Role>Intermediator</eb:Role>
    </eb:To>
<eb:CPAId>yoursandmycpa</eb:CPAId>
<eb:ConversationId>nnnnn</eb:ConversationId>
<eb:Service>Routing</eb:Service>
<eb:Action>ProcessInvoice</eb:Action>
<eb:MessageData>
     <eb:MessageId>1</eb:MessageId>
     <eb:Timestamp>2003-01-22T11:12:12+02</eb:Timestamp>
     <eb:RefToMessageId/>
</eb:MessageData>
</eb:MessageHeader>
</SOAP-ENV:Header>
<SOAP-ENV:Body>
<eb:Manifest eb:id="Manifest" eb:version="2.0">
<eb:Reference eb:id="Finvoice" xlink:href="20020209-133003">
<eb:schema eb:location="http://www.pankkiyhdistys.fi/verkkolasku/finvoice/finvoice.xsd" eb:version="2.0"/>
</eb:Reference>
</eb:Manifest>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
<?xml version="1.0" encoding="ISO-8859-1"?>


<!DOCTYPE Finvoice SYSTEM "Finvoice.dtd">
<?xml-stylesheet type="text/xsl" href="Finvoice.xsl"?>

<Finvoice Version="1.0">
     <SellerPartyDetails>
          <SellerPartyIdentifier>0123456-7</SellerPartyIdentifier>
          <SellerOrganisationName>Pullin Kala Oy</SellerOrganisationName>
          <SellerOrganisationTaxCode>0123456-7</SellerOrganisationTaxCode>
          <SellerPostalAddressDetails>
               <SellerStreetName>Haapatie 7</SellerStreetName>
               <SellerTownName>Helsinki</SellerTownName>
               <SellerPostCodeIdentifier>00100</SellerPostCodeIdentifier>
               <CountryCode>FI</CountryCode>
               <CountryName>FINLAND</CountryName>
               <SellerPostOfficeBoxIdentifier>PL 302</SellerPostOfficeBoxIdentifier>
          </SellerPostalAddressDetails>
     </SellerPartyDetails>
     <SellerContactPersonName>Hanna Paananen</SellerContactPersonName>
     <SellerCommunicationDetails>
          <SellerPhoneNumberIdentifier>050-5432659</SellerPhoneNumberIdentifier>
          <SellerEmailaddressIdentifier>[email protected]</SellerEmailaddressIdentifier>
     </SellerCommunicationDetails>
     <SellerInformationDetails>
          <SellerHomeTownName>Helsinki</SellerHomeTownName>
          <SellerVatRegistrationText>Alv.Rek</SellerVatRegistrationText>
          <SellerVatRegistrationDate Format="CCYYMMDD">19990321</SellerVatRegistrationDate>
          <SellerPhoneNumber>(09) 542 1222</SellerPhoneNumber>
          <SellerFaxNumber>(09) 542 2221</SellerFaxNumber>
          <SellerCommonEmailaddressIdentifier>[email protected]</SellerCommonEmailaddressIdentifier>
          <SellerWebaddressIdentifier>www.pullinkala.fi</SellerWebaddressIdentifier>
          <SellerAccountDetails>
               <SellerAccountID IdentificationSchemeName="IBAN">FI1234567890123456</SellerAccountID>
               <SellerBic IdentificationSchemeName="BIC">OKOYFIHH</SellerBic>
          </SellerAccountDetails>
          <SellerAccountDetails>
               <SellerAccountID IdentificationSchemeName="IBAN">FI1234567890123456</SellerAccountID>
               <SellerBic IdentificationSchemeName="BIC">NDEAFIHH</SellerBic>
          </SellerAccountDetails>
     </SellerInformationDetails>
     <BuyerPartyDetails>
          <BuyerPartyIdentifier>CL12221</BuyerPartyIdentifier>
          <BuyerOrganisationName>Kalakauppa Vilkkunen</BuyerOrganisationName>
          <BuyerPostalAddressDetails>
               <BuyerStreetName>Haapatie 1</BuyerStreetName>
               <BuyerTownName>Helsinki</BuyerTownName>
               <BuyerPostCodeIdentifier>00211</BuyerPostCodeIdentifier>
               <CountryCode/>
               <CountryName/>
               <BuyerPostOfficeBoxIdentifier/>
          </BuyerPostalAddressDetails>
     </BuyerPartyDetails>
     <BuyerContactPersonName>Maija Vikkunen</BuyerContactPersonName>
     <BuyerCommunicationDetails>
          <BuyerPhoneNumberIdentifier>(09)221222</BuyerPhoneNumberIdentifier>
          <BuyerEmailaddressIdentifier>[email protected]</BuyerEmailaddressIdentifier>
     </BuyerCommunicationDetails>
     <InvoiceDetails>
          <InvoiceTypeCode>INV01</InvoiceTypeCode>
          <InvoiceTypeText>LASKU</InvoiceTypeText>
          <OriginCode>Origin</OriginCode>
          <InvoiceNumber>1/2002</InvoiceNumber>
          <InvoiceDate Format="CCYYMMDD">20020612</InvoiceDate>
          <SellerReferenceIdentifier>212</SellerReferenceIdentifier>
          <OrderIdentifier>TI0988</OrderIdentifier>
          <InvoiceTotalVatExcludedAmount AmountCurrencyIdentifier="EUR">100,00</InvoiceTotalVatExcludedAmount>
          <InvoiceTotalVatAmount AmountCurrencyIdentifier="EUR">22,00</InvoiceTotalVatAmount>
          <InvoiceTotalVatIncludedAmount AmountCurrencyIdentifier="EUR">122,00</InvoiceTotalVatIncludedAmount>
          <ShortProposedAccountIdentifier>9922</ShortProposedAccountIdentifier>
          <NormalProposedAccountIdentifier>8822</NormalProposedAccountIdentifier>
          <AccountDimensionText>4500</AccountDimensionText>
          <VatSpecificationDetails>
               <VatBaseAmount AmountCurrencyIdentifier="EUR">100,00</VatBaseAmount>
               <VatRatePercent>22</VatRatePercent>
               <VatRateAmount AmountCurrencyIdentifier="EUR">22,00</VatRateAmount>
          </VatSpecificationDetails>
          <PaymentTermsDetails>
               <PaymentTermsFreeText>14 p�iv�� netto</PaymentTermsFreeText>
               <PaymentOverDueFineDetails>
                    <PaymentOverDueFineFreeText>Yliaikakorko 16%</PaymentOverDueFineFreeText>
                    <PaymentOverDueFinePercent>16</PaymentOverDueFinePercent>
               </PaymentOverDueFineDetails>
          </PaymentTermsDetails>
     </InvoiceDetails>
     <PaymentStatusDetails>
          <PaymentStatusCode>NOTPAID</PaymentStatusCode>
     </PaymentStatusDetails>
     <VirtualBankBarcode>250003210002229000122000000000000000862074102062800009</VirtualBankBarcode>
     <InvoiceRow>
          <ArticleIdentifier>123213123332123</ArticleIdentifier>
          <ArticleName>TUURA</ArticleName>
          <BuyerArticleIdentifier>1232321232332</BuyerArticleIdentifier>
          <DeliveredQuantity QuantityUnitCode="Kpl">10</DeliveredQuantity>
          <OrderedQuantity QuantityUnitCode="Kpl">10</OrderedQuantity>
          <UnitPriceAmount AmountCurrencyIdentifier="EUR" UnitPriceUnitCode="e/kpl">5,00</UnitPriceAmount>
          <RowIdentifier>221</RowIdentifier>
          <RowIdentifierDate Format="CCYYMMDD">20020611</RowIdentifierDate>
          <RowDeliveryDate Format="CCYYMMDD">20020615</RowDeliveryDate>
          <RowShortProposedAccountIdentifier>9922</RowShortProposedAccountIdentifier>
          <RowNormalProposedAccountIdentifier>8822</RowNormalProposedAccountIdentifier>
          <RowAccountDimensionText>4500</RowAccountDimensionText>
          <RowFreeText>Tuurat myyd��n varsien kanssa.</RowFreeText>
          <RowDiscountPercent>0</RowDiscountPercent>
          <RowVatRatePercent>22</RowVatRatePercent>
          <RowVatAmount AmountCurrencyIdentifier="EUR">11,00</RowVatAmount>
          <RowVatExcludedAmount AmountCurrencyIdentifier="EUR">50,00</RowVatExcludedAmount>
          <RowAmount AmountCurrencyIdentifier="EUR">61,00</RowAmount>
     </InvoiceRow>
     <InvoiceRow>
          <ArticleIdentifier>123213123332123</ArticleIdentifier>
          <ArticleName>HUOLLON VUOSIMAKSU</ArticleName>
          <StartDate Format="CCYYMMDDHHMMSS">20020611000000</StartDate>
          <EndDate Format="CCYYMMDDHHMMSS">2003062011000000</EndDate>
          <RowShortProposedAccountIdentifier>9923</RowShortProposedAccountIdentifier>
          <RowNormalProposedAccountIdentifier>8823</RowNormalProposedAccountIdentifier>
          <RowAccountDimensionText>4500</RowAccountDimensionText>
          <RowVatRatePercent>22</RowVatRatePercent>
          <RowVatAmount AmountCurrencyIdentifier="EUR">11,00</RowVatAmount>
          <RowVatExcludedAmount AmountCurrencyIdentifier="EUR">50,00</RowVatExcludedAmount>
          <RowAmount AmountCurrencyIdentifier="EUR">61,00</RowAmount>
     </InvoiceRow>
     <EpiDetails>
          <EpiIdentificationDetails>
               <EpiDate Format="CCYYMMDD">20020612</EpiDate>
               <EpiReference>1</EpiReference>
          </EpiIdentificationDetails>
          <EpiPartyDetails>
               <EpiBfiPartyDetails>
                    <EpiBfiIdentifier IdentificationSchemeName="BIC">OKOYFIHH</EpiBfiIdentifier>
               </EpiBfiPartyDetails>
               <EpiBeneficiaryPartyDetails>
                    <EpiNameAddressDetails>Pullin Kala</EpiNameAddressDetails>
                    <EpiAccountID IdentificationSchemeName="IBAN">FI1234567890123456</EpiAccountID>
               </EpiBeneficiaryPartyDetails>
          </EpiPartyDetails>
          <EpiPaymentInstructionDetails>
               <EpiRemittanceInfoIdentifier>8620741</EpiRemittanceInfoIdentifier>
               <EpiInstructedAmount AmountCurrencyIdentifier="EUR">122,00</EpiInstructedAmount>
               <EpiCharge ChargeOption="SHA">SHA</EpiCharge>
               <EpiDateOptionDate Format="CCYYMMDD">20020628</EpiDateOptionDate>
          </EpiPaymentInstructionDetails>
     </EpiDetails>
</Finvoice>

Converting String to SOAP Message

Hi,
I have a problem in conveting a String to SOAPMessage.Can anybody help in suggesting a way. or atleast make me known wether it is possible to do this or not.
-vyas

I don't think you can "convert" a String to a SOAP message. If you read the SOAP specification, http://www.www.w3.org/TR/2001/WD-soap12-part1-20011217/, you'll find that you'll have to decide where you want your String to go. If it is xml-formatted, a subelement of the SOAP body element would be a good place for it. If it is not an xml-formatted String, you will have to send it as an attachment.
Sun's JAX-RPC or JAXM is a good place to start.

Parse SOAP messages

Hi,
I would like to know how efficient would be to use Oracle Text to parse SOAP messages. The body of the SOAP messages are heterogeneous in terms of format and size (smallest messages is about 20 lines, biggest message is about 200 lines). The number of records to parse is approximately one hundred thousand every hour.
Thank you.

In what sense do you want to "parse" them? Do you just want to find individual strings in the SOAP messages, or are you looking to fully interpret the meaning and content of the SOAP messages? If it's the second of these, then Oracle Text is not the right solution - you could perhaps look at Oracle XML Database instead.

Need Code to Print SOAP Message

I'm using SAAJ to create SOAP messages and I'm looking for code that will print a SOAP message, including all tags, attributes, etc. as it would look if it had been hand-coded.
I've searched through this forum and found some similar posts, but the answers either just use the SOAPMessage writeTo() method, or do not print output formatted the way I want.
Is it possible to do this?
Thanks.

Hello.
Try this (soapMessage is your SoapMessage object instance that you created)
ByteArrayOutputStream outputStream = new ByteArrayOutputStream();
soapMessage.writeTo( outputStream );
byte[] byteArray = outputStream.toByteArray();
String soapMsg = new String( byteArray, "UTF-8");
// print the soapMsg
Hope this helps.

Putting a soap message in a variable to be sent

good day!..
i have this soap message that will be sent to a simple service provider simulator..
since this is only a simulation, i there will be only one service named leave (e.g. vacation leave, sick leave, etc.)
<?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:ns1="http://leaveprocessor.blueprints.jbi.sun.com/">
<soapenv:Body>
<ns1:processApplication>
<appName>applicant</appName>
<leaveType>type of leave</leaveType>
<numDays>number of days</numDays>
</ns1:processApplication>
</soapenv:Body>
</soapenv:Envelope>im using tcp for communication between my client and service provider..
basically, i have this code line that would stream my message to the service provider..
output.println(message);where output there is declared as:
output = new PrintStream(clientSocket.getOutputStream());i have successfully streamed my message to the service provider when i assigned it a string value like the word "dog"
but what i want to happen is that the message will have the value of the soap message stated above..
how can i do that?
any help in solving this problem will be greatly appreciated..
thanx!..
God bless!..

HI,
I opened a "Read Me" in TextEdit and copied the whole text.
I sent to my iPhone and it got broken up into 4 separate pieces to be delivered but there seemed to be no delay in receiving them rather than just a single message.
I am finding a delay though on some text messages.
9:40 PM Wednesday; July 25, 2012
Please, if posting Logs, do not post any Log info after the line "Binary Images for iChat"
 iMac 2.5Ghz 5i 2011 (Lion 10.7.2)
 G4/1GhzDual MDD (Leopard 10.5.8)
 MacBookPro 2Gb (Snow Leopard 10.6.8)
 Mac OS X (10.6.8),
"Limit the Logs to the Bits above Binary Images."  No, Seriously

I can not find the messages in sxmb_moni in http to rfc scenarion

hi i'm using http client tool when i send the message its working fine i'm getting the response, but i can not find that message in sxmb_moni in http to rfc scenario
can anyone help me

Hi lnaki vila
I'm using pi 7.0 version
i can see the other scenarios like SOAP to RFC, SOAP to IDOC,FILEto IDOC
in sender side i'm not using any communication channel and adapter engine i'm just using http client tool for testing purpose
i'm getting the response that's fine because its a synchronous communication
i checked sxmb_adm in that -->integration configuration LOGGING parameter of category RUNTIME is set to ENGINE_TYPE and current value is HUB(Integration server)
thanks in advance
regards
Satish

Can not find some messages in Mail using search

I have some problems with Mail.app I can not find some messages in Mail using search, the strange thing is that sometimes mail search finds some messages, but after rebuilding spotlight index the search displays other messages with the all messages searched using same search criteria. I have also tried to delete Envelope index file from the Mail folder in usr/library and forced mail to import all mailboxes but it started to crash importing some of mailboxes - I deleted the messages from that mailboxes, imported remaining mailboxes and tried to rebuild mailbox, but everything without a successes. Any ideas how to solve it?

Hi lnaki vila
I'm using pi 7.0 version
i can see the other scenarios like SOAP to RFC, SOAP to IDOC,FILEto IDOC
in sender side i'm not using any communication channel and adapter engine i'm just using http client tool for testing purpose
i'm getting the response that's fine because its a synchronous communication
i checked sxmb_adm in that -->integration configuration LOGGING parameter of category RUNTIME is set to ENGINE_TYPE and current value is HUB(Integration server)
thanks in advance
regards
Satish

Writting attached file from SOAP message to a FTP folder

Hi everybody,
Our scenario is an interface which receives a SOAP message with a file attached. As we don't need to do any mapping into the attachment, we are supposed to deliver that file as it is into a FTP folder.
Our problem is that we cannot find how to configure File comm channel to write the attached file and no the SOAP XML message which is what we are getting now. Any help on this?
Thanks in advance.

Hi
check these forum posts
SOAP with attachments
Mail Sender Adapter - Attachment Handling
Regards
Vishnu

Find Soap Message Output Format

Similar Messages

Maybe you are looking for