MessageContext.getMessage().toString() is not giving soap message

Hi,
I have implemented a handler for JAX-RPC web service on weblogic 10.3 and my code in handler is exactly same as below.
public boolean handleRequest(MessageContext context) {
SOAPMessageContext messageContext = (SOAPMessageContext) context;
System.out.println("** Request: "+messageContext.getMessage().toString());
log.info(messageContext.getMessage().toString());
return true;
and It is not printing complete SOAP message. Instead it is just printing something like .."weblogic.xml.saaj.SOAPMessageImpl@a050277". I feel this is some issue with classpath setting. can somebody please assist with this?

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

Similar Messages

  • IDOC_INPUT_DEBITOR not giving sucees Message

    Hi ,
    We are using FM 'IDOC_INPUT_DEBITOR' for posting customer. Inside this FM, SAP does Call Transaction XD01 and collects the messages in BDCMSGCOLL.
    Our logic is based on the Success message that this FM generates and that found in this BDCMSGCOLL. Till few days it was working fine but now this FM is not returning any message even though the customer is getting created. I ran in the foreground / Error/background mode, but even though I found the customer in KNA1, this FM is not returning any Success message.
    All Error & Information messages are coming but not the Success. Our further processing heavily depends on the message type and hence the problem.
    We are on ERP 2004 and as told it was working fine few days back. I wanted to know what changes would have made the FM to behave like this. As there are many users for this System, I can’t find who changed what.  If some one has faced  this issue or have some ides, pls guide me.
    Thanks for listening.
    Regds
    Harish

    Thanks Gareth for the reply. This is standard FM and after the Call transaction, SAP code reads the  BDCMSGCOLL. If it does not found ans S in that, it fails the IDOC to 51 status.  There is no Z code in this.
    I would like to know what config changes can supress the success message . I tried doing BDC thoguth SM35 and there also found that no message is coming when the Customer is created. This would mean that there is something worng in srrting rather than FM and BDC which is causing the BDC failure in Std FM.
    Regds
    Harish

  • Dynamic Credit Limit check not giving error message

    Hi!
    I have configured the credit management like below:
    1. high risk, medium risk, low risk category.
    2. credit control area with update : 00000012
    3. In pricin procedure for net value, routine "A" is given.
    4. In Item Category, Credit Active tick mark is checked.
    3. Assigned D,  credit group 01(Credit Group for Sales Order)  in sales document types.
    4. assigned credit group in Delivery document types.
    5. configured automatic credit control;
    for high risk, with credit group 01 , dynamic check  with reaction D , and status/block tick by considering open order and open deliveries .
    My main aim is when sale order is creating, system should give error message , when credit limit is exceeded.
    But system is giving following information message only:
         Dynamic credit check: credit limit exceeded (data
         cannot be saved)
         250.00 USD
    that is only information message and allowing to save the sael order and delivery also.
    can any one give idea where config is missed.
    we have activated FSCM also, but no link to credit control area.
    regs,
    ramesh

    Hi,
    Check up at message control with OBA5
    Regards
    VG

  • SOAP Message Handler

    I have a stand-alone java client which invokes a WSE enabled .NET web service. A custom policy file (no encryption or certificate. Just username token) is associated with the java client. I also include a SOAP handler to display the SOAP request. When I ran the client,
    the display of the SOAP request message was quite different between the console and the .NET server trace file. The statement "messageContext.getMessage().toString());" just display "weblogic.xml.saaj.SOAPMessageImpl@502e15"
    Could some one please tell me why the SOAP handler did not display the rest of the SOAP message like the .NET server trace file (shown below)?
    Here is a snippet of my SOAP Handler handleRequest implementation:
    public boolean handleRequest(MessageContext context) {
    System.out.println("handle request...");
    SOAPMessageContext messageContext = (SOAPMessageContext) context;
    System.out.println("** Request: " + messageContext.getMessage().toString());
    SOAPHeader sh = null;
    try {
    sh = messageContext.getMessage().getSOAPHeader();
    } catch (SOAPException se) {
    Iterator it = sh.examineAllHeaderElements();
    while (it.hasNext()) {
    System.out.println("*** There are SOAP Headers.....");
    SOAPHeaderElement elem = (SOAPHeaderElement)it.next();
    System.out.println("header ==> " + elem.getElementName().getQualifiedName());
    return true;
    Here is the display on the console:
    run:
    [java] in class digimarc.foto.webservice.clientstub.ClientHandler init()
    [java] in class digimarc.foto.webservice.clientstub.ClientHandler init()
    [java] in class digimarc.foto.webservice.clientstub.ClientHandler init()
    [java] handle request...
    [java] ** Request: weblogic.xml.saaj.SOAPMessageImpl@502e15
    [java] *** There are SOAP Headers.....
    [java] header ==> wsse:Security
    [java] <11-Apr-2008 2:14:04 o'clock PM ADT> <Info> <WebService-LogHandler> <BEA-000000> <weblogic.xml.saaj.SOAPMessageImpl@502e15>
    [java] ** Fault: weblogic.xml.saaj.SOAPMessageImpl@57b10b
    [java] <11-Apr-2008 2:14:06 o'clock PM ADT> <Info> <WebService-LogHandler> <BEA-000000> <weblogic.xml.saaj.SOAPMessageImpl@57b10b>
    [java] fetchMostRecent() Failed...
    .NET web server trace:
    <inputMessage utc="3/28/2008 3:05:43 PM" messageId="urn:uuid:23052686-df58-4144-9ec9-52617e5b5cd6">
    <processingStep description="Unprocessed message">
    <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
    <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">
    <wsse:UsernameToken wsu:Id="unt_R4qflJg2MR0no0AY" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
    <wsse:Username>nbddls\john</wsse:Username>
    <wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">G0ggin!</wsse:Password>
    </wsse:UsernameToken>
    </wsse:Security>
    </env:Header>
    <env:Body>
    <m:ImagingFolioFetchMostRecent xmlns:m="urn:digimarc.com:ImageServer:WebServices">
    <m:personID>1001917</m:personID>
    </m:ImagingFolioFetchMostRecent>
    </env:Body>
    </env:Envelope>
    </processingStep>
    </inputMessage>

    But when i am calling the sevrice the client side
    handler is not creating the soap envlope it is
    showing it as null.
    Follwing are the errors on Sun ONE console.The stack trace appears to be coming from the server side, not the client side. Then you get another error on the client side when the first error comes back. Without the line numbers in the file, I can't be positive, but it looks like the NPE is coming from the it.next() call below in your server handler:
    Iterator it=header.getChildElements(name);
    SOAPHeaderElement she= (SOAPHeaderElement)it.next();
    It would be good to see the message on the wire to be sure, but this prolly means you have no header elements. Maybe the setMessage call on the client side handler isn't working -- are you sure that the client handler is being invoked? I don't see the "***Client***" message anywhere in the output.
    If so, you could always try getting the existing soap message from the context and add headers to instead of creating a new message. The new message won't have the contents that you want to send to the service, so it looks like the call would fail even if the handler finishes correctly.
    Cheers,
    Bobby

  • Client intercept SOAP message

    We are developing a client application which accesses Web Services. I have been told to log all and every SOAP message it sends or receives.
    My client connects the Web Service through an static proxy we created using WSDL2Java(Axis). How could I get the SOAP messages (in the client side)?
    At this point we can't change the JAX-RPC client to pure SOAP nor the static proxy to a dynamic one (the application is almost finished and we are a bit short in time).
    We have been searching (google) and I have found this:
    http://e-docs.bea.com/wls/docs81/webserv/interceptors.html
    It says it is possible to do what I need by using a javax.xml.rpc.handler.Handler implementation class, but when I have tried to add the handler to the Web Service client it plainly ignores my handler.
    Does anybody know how to specify a handler to "intercept" the incoming server SOAP messages? (The server is a 3rd party (so we have no access at all to its source code)).
    This is my handler:
    import javax.xml.namespace.QName;
    import javax.xml.rpc.handler.Handler;
    import javax.xml.rpc.handler.HandlerInfo;
    import javax.xml.rpc.handler.MessageContext;
    import javax.xml.rpc.handler.soap.SOAPMessageContext;
    public class MyHandler implements Handler{
    private HandlerInfo handlerInfo;
    public MyHandler() {
         super();
    public boolean handleRequest(MessageContext arg0) {
         SOAPMessageContext messageContext = (SOAPMessageContext) arg0;
         System.out.println("** Request: "+messageContext.getMessage().toString());
         return true;
    public boolean handleResponse(MessageContext arg0) {
         SOAPMessageContext messageContext = (SOAPMessageContext) arg0;
         System.out.println("** Response: "+messageContext.getMessage().toString());
         return true;
    public boolean handleFault(MessageContext arg0) {
         SOAPMessageContext messageContext = (SOAPMessageContext) arg0;
         System.out.println("** Fault: "+messageContext.getMessage().toString());
         return true;
    public void init(HandlerInfo arg0) {
         this.handlerInfo = arg0;
    public void destroy() {
    public QName[] getHeaders() {
         return handlerInfo.getHeaders();
    I try to add it to the Web Service client by doing this:
    ServiceServiceLocator locator = new ServiceServiceLocator();
    try {
    Service port = locator.getws();
    // To obtain the SOAP messages
    QName portName = new QName( "http://endpoint_WS", "wsHello");
    HandlerRegistry registry = locator.getHandlerRegistry();
    List handlerList = new ArrayList();
    handlerList.add( new HandlerInfo( MyHandler.class, null, null ) );
    registry.setHandlerChain( portName, handlerList );
    port.sayHelloTo("Peter");
    Anybody knows where am I mistaken?
    I am trying to avoid modifying the generated client (static) proxy, the Web Service is still in development and it would mean I would have to edit it always they change the Web Service (leading to a lot of wasted work).

    I managed to intercept messages SOAP without proxy, but I do not obtain it with proxy (JAX-RPC or Axis)
    Any Suggest?
    Thank you.

  • How to get full SOAP message in WebService

    hi,
    Is it possible to get SOAP message while Request operation during transaction in WebService.
    I tried with Handler, while retreiving message it is having a MessageContext. How to initilize that like example
    public boolean handleRequest(MessageContext mc) {
              SOAPMessageContext messageContext = (SOAPMessageContext) mc; 
              System.out.println("** Request: "+ messageContext.getMessage().toString());
              return true;
         }while i make a class called SoapHdlr i have implemented all methods including the above.
    In that from my class if i want to call the above method i need to pass MessageContext how to give that MessageContext or any other ways to get SOAPMessage fully.
    plz can any one guide me there
    ThanKQ

    I think, there are some concepts missunderstood. First if you use JAX-WS- Metro framework, this kind of handlers will work. Also you should identify your SOAPHandler for your web service. For ex: in Netbeans 6, you can right click on service and select configure handlers. Then you decide your handler.
    Then automatically, Metro framework directs SOAPMessages to your SOAPHandler to handle full SOAPs. HandleMessage() method will work.
    If you have problem again, just ask.

  • How to include XML Prolog in BPEL SOAP message.

    Hi,
    I'm using SOA Suite 11g on WebLogic and have a BPEL Process in a composite application that is calling a third party SOAP Web Service.
    Whilst it is standard for a SOAP service to not care whether or not the SOAP message includes an XML Prolog (<?xml version="1.0" encoding="utf-8"?>) this third party service rejects the message if the prolog is not included.
    Unfortunately the partner link in my BPEL process is not adding the prolog when invoking the service and I cannot get the third party service changed to accept messages without it.
    Does anyone know how I can make BPEL include the prolog in SOAP messages?
    Currently the SOAP message looks like this:-
    <soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope">
    <soap:Header/>
    <soap:Body>
    </soap:Body>
    </soap:Envelope>
    What I would like it to look like is this :-
    *<?xml version="1.0" encoding="utf-8"?>*
    <soap:Envelope xmlns:soap="http://www.w3.org/2003/05/soap-envelope">
    <soap:Header/>
    <soap:Body>
    </soap:Body>
    </soap:Envelope>
    Thanks in advance...

    Hi swigg,
    It's not the partnerlink input variable that I want to manipulate, it's the SOAP Envelope that the Partner Link generates when it is invoked.
    I know that you can manipulate the SOAP Header by adding properties to the Partnerlink but it's the Envelope that surrounds both the Header and the Body that I want to set the prolog on.
    It can be done in java and .NET (WCF) by setting a property on the SOAP Envelope class, but I can't see a way to do it for a partner link in BPEL which is a shame.
    To be honest it looks like Oracle have let me down here so I'll have to use some other technology to call this service which unfortunately plays into the hands of those that didn't think I should use Oracle's BPEL offering in the first place.
    Thanks.

  • Serialization of SOAP message in WL 7.1 (without toString)

    Hi all.
    I'm using Weblogic 7.1 and am trying to serialize the SOAP message I get in my
    request handler to raw XML. Unfortunately since WL 7.1 only seems to support an
    old version of SAAJ, that for some bizarre reason doesn't use the DOM interfaces,
    the only way I can think of to do this is to call toString() on the message. Of
    course I'd rather not do this since this is making assumptions about the WL implementation
    of SAAJ. Can anyone think of a better way of doing this?
    Since all I'm after is the raw XML anyway, would it make sense to just pass this
    in as a string in the RPC call (given that my messages are likely to be fairly
    big -- around 500K of raw XML)? Obviously this is a total hack, and I probably
    won't end up doing it, but does anyone know of any good technical reasons why
    I shouldn't do this?
    Thanks.
    Neil.

    Hi Neil
    Manoj has an WLS 7.x example passing XML without data bindings [1] that
    may assist your efforts. Also see the example using handlers to get the
    SOAP request/response message.
    Regards,
    Bruce
    [1]
    http://manojc.com/?wls70/sample2
    [2]
    http://manojc.com/?wls70/sample4
    Neil wrote:
    >
    Hi all.
    I'm using Weblogic 7.1 and am trying to serialize the SOAP message I get in my
    request handler to raw XML. Unfortunately since WL 7.1 only seems to support an
    old version of SAAJ, that for some bizarre reason doesn't use the DOM interfaces,
    the only way I can think of to do this is to call toString() on the message. Of
    course I'd rather not do this since this is making assumptions about the WL implementation
    of SAAJ. Can anyone think of a better way of doing this?
    Since all I'm after is the raw XML anyway, would it make sense to just pass this
    in as a string in the RPC call (given that my messages are likely to be fairly
    big -- around 500K of raw XML)? Obviously this is a total hack, and I probably
    won't end up doing it, but does anyone know of any good technical reasons why
    I shouldn't do this?
    Thanks.
    Neil.

  • Signing a soap message seems to not work in jwsdp14

    I'm trying to sign a soap message according to the latest oasis specifications (http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0.pdf) using the libraries provided with jwsdp14 (mainly xmlsec.jar).
    As far as I know, there is not yet documention/example about this specific issue.
    The following is the code I have to sign a soap message: it seems to work fine because the signed soap message respects the above specifications... but what I notice is that the digest and the signature values it contains are always the same, I mean: if i change the source soap message, the signed soap message in output is always the same!
    Any clue??
    import com.sun.org.apache.xml.security.Init;
    import com.sun.org.apache.xml.security.signature.XMLSignature;
    import com.sun.org.apache.xml.security.transforms.Transforms;
    import com.sun.org.apache.xml.security.utils.Constants;
    import com.sun.xml.wss.*;
    import com.sun.xml.wss.reference.DirectReference;
    import org.w3c.dom.Document;
    import javax.xml.soap.SOAPHeader;
    import javax.xml.soap.SOAPMessage;
    import javax.xml.soap.SOAPBody;
    import java.io.File;
    import java.io.FileInputStream;
    import java.io.FileOutputStream;
    import java.security.PrivateKey;
    import java.security.cert.X509Certificate;
    public class Main {
    public static void main(String[] args) {
    // The file from which we will load the sample SOAP message
    String fileName = "F:\\SampleSoapMessage.xml";
    // Store the WSSE signed message here
    String signatureFileName = "F:\\SignedSampleSoapMessage.xml";
    try {
    // Initialize the apache libraries
    Init.init();
    // Obtain security elements from the keystore
    PrivateKey privateKey = MySecurityUtils.getPrivateKey();
    X509Certificate cert = MySecurityUtils.getCertificate();
    // Obtain a sample SOAPMessage from a file
    FileInputStream fis = new FileInputStream(new File(fileName));
    Document doc = XMLUtil.toDOMDocument(fis);
    SOAPMessage message = MyFileUtils.getMessageFromFile(doc);
    SOAPHeader header = message.getSOAPHeader();
    SOAPBody body = message.getSOAPBody();
    // Set the wsu:Id attribute to the Body
    XMLUtil.setWsuIdAttr(body, "MyId");
    // Create a WSSE context for the SOAP message
    SecurableSoapMessage sssm = new SecurableSoapMessage(message);
    // Create a security header for the message (<wsse:Security>)
    SecurityHeader sh = sssm.findOrCreateSecurityHeader();
    // Insert the certificate (<wsse:BinarySecurityToken>)
    X509SecurityToken stoken = new X509SecurityToken(header.getOwnerDocument(), cert, "X509TokenRef");
    sh.insertHeaderBlock(stoken);
    // Insert the keyinfo referring to the certificate (<ds:KeyInfo>)
    KeyInfoHeaderBlock kihb = new KeyInfoHeaderBlock(header.getOwnerDocument());
    SecurityTokenReference secTR = new SecurityTokenReference(header.getOwnerDocument());
    DirectReference dirRef = new DirectReference();
    dirRef.setURI("#X509TokenRef");
    secTR.setReference(dirRef);
    kihb.addSecurityTokenReference(secTR);
    //sh.insertHeaderBlock(kihb);
    // Insert the Signature block (<ds:Signature>)
    SignatureHeaderBlock shb = new SignatureHeaderBlock(header.getOwnerDocument(), XMLSignature.ALGO_ID_SIGNATURE_RSA);
    Transforms transforms = new Transforms(header.getOwnerDocument());
    transforms.addTransform(Transforms.TRANSFORM_C14N_EXCL_OMIT_COMMENTS);
    shb.addSignedInfoReference("#MyId", transforms, Constants.ALGO_ID_DIGEST_SHA1);
    shb.addChildElement(kihb.getAsSoapElement());
    sh.insertHeaderBlock(shb);
    // Digest all References (#MyId) in the SignedInfo, calculate the signature value
    // and set it in the SignatureValue Element
    shb.sign(privateKey);
    // Add the signature data to the header element
    header.addChildElement(sh.getAsSoapElement());
    // Save the signed SOAP message
    FileOutputStream fos = new FileOutputStream(new File(signatureFileName));
    message.writeTo(fos);
    message.writeTo(System.out);
    } catch (Exception exc) {
    exc.printStackTrace();
    System.out.println("An error has occurred : " + exc.toString());
    PS: Classes MySecurityUtils and MyFileUtils are not included since they have nothing interesting.
    The sample input sopa message is:
    <?xml version="1.0" encoding="UTF-8"?>
    <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
    <SOAP-ENV:Header>
    </SOAP-ENV:Header>
    <SOAP-ENV:Body>
    <Intestazione>
    </Intestazione>
    </SOAP-ENV:Body>
    </SOAP-ENV:Envelope>
    and the output signed sample message is:
    <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
    <SOAP-ENV:Header>
    <wsse:Security SOAP-ENV:mustUnderstand="1" xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"><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="#MyId">
    <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>2jmj7l5rSw0yVb/vlWAYkK/YBwk=</ds:DigestValue>
    </ds:Reference>
    </ds:SignedInfo>
    <ds:SignatureValue>
    YdKNSPWnx630AYeZ6AXVco1b0RMo8C3WWbziq7C009gg4nhknEZmH0ds78y328SgAlAAVR6Swwok
    HE3OWgL8TZ1Ks0IimmmDd8/XIb2KlfiqnUNtTjGjUn9FLQEv/CMbmrCr7EO9rf/N+0cyAyGzrKo5
    ieEQhtZy9uZAKh2mrmM=
    </ds:SignatureValue>
    <ds:KeyInfo>
    <wsse:SecurityTokenReference>
    <wsse:Reference URI="#X509TokenRef"/>
    </wsse:SecurityTokenReference>
    </ds:KeyInfo></ds:Signature><wsse:BinarySecurityToken EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary" ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3" xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="X509TokenRef">MIIDITCCAsugAwIBAgIQIdu5EMFuQntM5IBOMeFcETANBgkqhkiG9w0BAQUFADCBqTEWMBQGA1UE
    ChMNVmVyaVNpZ24sIEluYzFHMEUGA1UECxM+d3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5L1Rl
    c3RDUFMgSW5jb3JwLiBCeSBSZWYuIExpYWIuIExURC4xRjBEBgNVBAsTPUZvciBWZXJpU2lnbiBh
    dXRob3JpemVkIHRlc3Rpbmcgb25seS4gTm8gYXNzdXJhbmNlcyAoQylWUzE5OTcwHhcNMDQwODA1
    MDAwMDAwWhcNMDQwODE5MjM1OTU5WjBhMQswCQYDVQQGEwJJVDENMAsGA1UECBMEUk9NQTENMAsG
    A1UEBxQEcm9tYTEOMAwGA1UEChQFaXNzcGExDjAMBgNVBAsUBWNoaWVmMRQwEgYDVQQDFAt3d3cu
    dGVzdC5pdDCBnzANBgkqhkiG9w0BAQEFAAOBjQAwgYkCgYEAtIsomDk9VthgMorPmG0dAwqLtTBi
    U69liwopwrnAbtzIiO56R9yh4tXvG9+QWtEFRcDHVwWi9YdaHQFCvjymnNYDUHkpJsWp11nIAfOA
    k+d9v1YDje4S6oba7tsIJSEkUu7LQ888Q3cGt/KUaEu6b0lZJ5zY9slK0onUPeTB3e8CAwEAAaOB
    0TCBzjAJBgNVHRMEAjAAMAsGA1UdDwQEAwIFoDBCBgNVHR8EOzA5MDegNaAzhjFodHRwOi8vY3Js
    LnZlcmlzaWduLmNvbS9TZWN1cmVTZXJ2ZXJUZXN0aW5nQ0EuY3JsMFEGA1UdIARKMEgwRgYKYIZI
    AYb4RQEHFTA4MDYGCCsGAQUFBwIBFipodHRwOi8vd3d3LnZlcmlzaWduLmNvbS9yZXBvc2l0b3J5
    L1Rlc3RDUFMwHQYDVR0lBBYwFAYIKwYBBQUHAwEGCCsGAQUFBwMCMA0GCSqGSIb3DQEBBQUAA0EA
    Y66OqTOpHcpNUPlD4A38s8bPIIjrf+C+Wv08lUj+DGN5pm+gBWdbWEGaQmqU8fPPtGrQnHz2NAUr
    ZmLaEw/qKw==</wsse:BinarySecurityToken></wsse:Security></SOAP-ENV:Header>
    <SOAP-ENV:Body xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="MyId">
    <aTag>
    <aChild>a value</aChild>
    </aTag>
    </SOAP-ENV:Body>
    </SOAP-ENV:Envelope>
    NOTE: Check the value of <ds:SignatureValue> and <ds:DigestValue>: they never change even if I change the body of the source message.

    Quoting Farrukh's reply to this question on java.net -
    I can share some examples of how I have used JWSDP 1.4 and XML DSIG API to sign and verify a "standalone" soap message with and without mime attachments.
    Please see the following Utility class written for the freebXML Registry project [1] for an example of how to do what you seek:
    http://cvs.sourceforge.net/viewcvs.py/ebxmlrr/omar/src/java/org/freebxml/omar/common/security/SecurityUtil.java?view=markup
    See methods signSOAPMessage(...), signPayload(...), verifySOAPMessage(...) and verifyPayloadSignature(...)
    What you are trying to do is definitely doable and has been done with JWSDP 1.4. In my experience XML DSIG API met my needs very well.
    Best of luck.
    [1] freebXML Registry Project:
    http://ebxmlrr.sourceforge.net
    ---------------------------------------------------------------------------------

  • I have a 16GB 3GS phone. For the last few days, my phone is constantly giving me message that the accessory attached to my phone is not optimized for this iphone. You may experience noise or poor communication, while there is no acessory attached to it.

    I have a 16GB 3GS phone since about20 months now. For the last few days, my phone is constantly giving me message that the accessory attached to my phone is not optimized for this iphone. You may experience noise or poor communication, while there is no acessory attached to it. I always used standard headphones and charging cable. Now when i recall, it started at one of the sync sessions with my itunes. I have turned my phone off and aon again and again but the message keeps coming every one or two minutes.I have also started loosing voicce on different applications like youtube etc. Also the ringer volume up and down key does not show me the small boxes increasing or decreasing on screen. The phone is playing crazy. Can someone help please
    Thanks
    Zia

    It helped earlier but it has come back again. I don't know what to do. I tried what you said earlier but this time even this is not working either. And quite intrestingly my phone won't turn off. I turn it off, it goes off and then restarts on its own and then keep giving the same message again and again.
    Could it be a charging cable, is there any chance that the cable which was working fine one day could turn to be "incompatible" with iphone the other day????????
    Please help

  • Samsung note 3 is not giving audible alerts for all my text messages since the 4.4.4 update.

    Samsung note 3 is not giving audible alerts for all my text messages since the 4.4.4 update.  I get an audible tone about 3/4 of the time.  Thinking a conversation is over I come back 45 minutes later to find another text I didn't know came in.  I've restarted my phone and checked my message settings.   Any ideas?  Factory reset is not an option!

    I'd try going back into the Text Message settings. In Sound setting, work the setting from None to an alert. Then in Vibrate put a check in the box then uncheck. Just to see if that will free it up, could be a possible corruption with the new software update?

  • Message Envelope not found. Probably empty soap message. Error while testing web service

    Hi Gurus,
    I'm new to web service.
    I have created an RFC and a web service to create a pdf.  When I try to test the web service, I'm getting an error : "Message Envelope not found. Probably empty soap message." I have tried all the links available in google, but i'm unable to resolve the issue.
    Can anyone help me to solve this.
    Many thanks in advance.

    Which version/platform are you using?
    The thing you need to consider here is that the JDev proxy settings do not affect the BPEL server.
    So if the BPEL server cannot connect to your webservice, it will not be because of any Jdev setting.
    Check the proxy settings on your BPEL server (on 10.1.2 developer install it will be in obsetenv.bat, on 10.1.3 it will be a commandline property of the JVM - see AS Control administration page for the JVM)

  • HT1483 my iPod is not responding. It is giving a message low battery, please wait and is displaying the apple support link

    my ipod is not responding. It is giving a message pleases wait low battery and showing me a link to apple support 

    Hey,
    Welcome to Apple Support Communities.
    Well leave it for few minutes then try plugging it to the charger, if that does not work. Try restoring it from revious backup. This will change the software and hopefully earase the error. If that did not fix it i guess you need to take it to the Store for a check.
    I really hope this helps you. Let me know if it does. If not feel free to give me a shout. Best of luck.

  • [NOTE] Adding xsi type to SOAP messages

    Here is a quick 2.0.10 note.
    Some older SOAP stack require xsi type information embedded in the SOAP message to unmarshall the XML message into the appropriate object representation.
    Most customers do no want the overhead of xsi type definition into the SOAP message given that most modern SOAP stack perform the unmarshalling based on the WSDL/XML Schema.
    To address both requirements, we now by default do not add the xsi:type information to the SOAP traffic that the BPEL PM server generates.
    But we have added a new configuration property to the partnerLinkBinding element of the bpel.xml deployment descriptor so that you can ask the BPEL PM server to selectively decorate the SOAP messages targeted at a specific partnerLink. Here is how this looks like:
    <partnerLinkBinding name="XXXXX">
    <property name="sendXSIType">true</property>
    </partnerLinkBinding>
    Note: the challenge here is that if you invoke a service that requires XSI type information and you forget to set that flag in the deployment descriptor you will get a BindingFault with no detail :-( We are very aware of this limitation and are working very diligently towards addressing this problem with a much nicer error message in the 2.1 (aka end of September release).
    Edwin

    Hi,
    thanks for the quick answers.
    The Werbservice is MS CRM Dynamics. The "GUI" is still working. so the webservice is active and alive.
    I want to query the CRM, so i sent a fetch statement to file, which is being picked up and sent as SOAP message to the webservice.
    With point 6 in the mentioned blog the error message in the rwb is gone now, but the message in SXMB_MONI is flagged red and i'm struggling to finfd out what the next error is....may be someone can point out where to look at

  • Could not access SOAP header - sending sopa message using weblogic

    i am using saaj to send a SOAP message ,through weblogic, i am getting an error like below
    Could not access SOAP header
    what should i do for sending a soap message using weblogic

    You're going to have to provide many more details than that. If it's useful, you could go here and read all the documentation books covering web services.

Maybe you are looking for