balachandran ajanthan created RAMPART-418:
---------------------------------------------

             Summary: Adding custom soap header fails with rampart
                 Key: RAMPART-418
                 URL: https://issues.apache.org/jira/browse/RAMPART-418
             Project: Rampart
          Issue Type: Bug
          Components: rampart-core
    Affects Versions: 1.6.1
            Reporter: balachandran ajanthan
             Fix For: 1.6.3


Adding custom header as bellow fails with following exception[0] when the 
rampart is engaged in a client.

 OMFactory omFactory =OMAbstractFactory.getOMFactory();
    OMNamespace omNamespace = 
omFactory.createOMNamespace("http://example.com/...";, "sp");
    OMElement header = omFactory.createOMElement("sptest", omNamespace);
    header.setText("test");
    stub._getServiceClient().addHeader(header);

[0]
Caused by: org.apache.rampart.RampartException: Error in extracting message 
properties
    at org.apache.rampart.RampartMessageData.<init>(RampartMessageData.java:379)
    at org.apache.rampart.MessageBuilder.build(MessageBuilder.java:61)
    at org.apache.rampart.handler.RampartSender.invoke(RampartSender.java:65)
    ... 10 more
Caused by: org.apache.ws.security.WSSecurityException: Error in converting SOAP 
Envelope to Document; nested exception is: 
    java.lang.ClassCastException: org.apache.axiom.om.impl.llom.OMElementImpl 
cannot be cast to org.apache.axiom.soap.SOAPHeaderBlock
    at 
org.apache.rampart.util.Axis2Util.getDocumentFromSOAPEnvelope(Axis2Util.java:191)
    at org.apache.rampart.RampartMessageData.<init>(RampartMessageData.java:270)
    ... 12 more
Caused by: java.lang.ClassCastException: 
org.apache.axiom.om.impl.llom.OMElementImpl cannot be cast to 
org.apache.axiom.soap.SOAPHeaderBlock
    at 
org.apache.rampart.util.Axis2Util.getDocumentFromSOAPEnvelope(Axis2Util.java:141)
    ... 13 more



--
This message was sent by Atlassian JIRA
(v6.2#6252)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to