SoapHeaderTest fails when Rampart is engaged
--------------------------------------------

                 Key: ODE-398
                 URL: https://issues.apache.org/jira/browse/ODE-398
             Project: ODE
          Issue Type: Bug
          Components: Axis2 Integration
            Reporter: Alexis Midon
             Fix For: 1.3


SoapHeaderTest fails with the traces below when Rampart is engaged.

To reproduce, engage module globally in axis2.xml or roll back branch 1.X to 
revision r705826

DEBUG - GeronimoLog.debug(66) | Sending a message containing wsa endpoints in 
headers for session passing.
DEBUG - GeronimoLog.debug(66) | <?xml version='1.0' 
encoding='utf-8'?><soapenv:Envelope 
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";><soapenv:Header><ConversationId
 xmlns="http://my.company/super/protocol"; 
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"; 
xmlns:myns="http://my.company/super/protocol";>ZZZXYZ</ConversationId><addr:To 
xmlns:addr="http://www.w3.org/2005/08/addressing";>http://localhost:8888/processes/DummyService</addr:To><addr:Action
 
xmlns:addr="http://www.w3.org/2005/08/addressing";>urn:faultTest</addr:Action><addr:ReplyTo
 
xmlns:addr="http://www.w3.org/2005/08/addressing";><addr:Address>http://www.w3.org/2005/08/addressing/anonymous</addr:Address></addr:ReplyTo><addr:MessageID
 
xmlns:addr="http://www.w3.org/2005/08/addressing";>uuid:hqejbhcnphr3oped29htmi</addr:MessageID></soapenv:Header><soapenv:Body><faultTest
 xmlns="http://axis2.ode.apache.org";><dummy:in 
xmlns:dummy="http://axis2.ode.apache.org";>Hello</dummy:in></faultTest></soapenv:Body></soapenv:Envelope>
ERROR - GeronimoLog.error(108) | Error sending message 
(mex={PartnerRoleMex#hqejbhcnphr3oped29htmg [PID 
{http://ode/bpel/unit-test}HeaderTest-1] calling [EMAIL PROTECTED](...)}): 
Error in extracting message properties
org.apache.axis2.AxisFault: Error in extracting message properties
        at 
org.apache.rampart.handler.RampartSender.invoke(RampartSender.java:70)
        at org.apache.axis2.engine.Phase.invoke(Phase.java:292)
        at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:212)
        at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:377)
        at 
org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:374)
        at 
org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:211)
        at 
org.apache.axis2.client.OperationClient.execute(OperationClient.java:163)
        at 
org.apache.ode.axis2.SoapExternalService$1$1.call(SoapExternalService.java:178)
        at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
        at java.util.concurrent.FutureTask.run(FutureTask.java:138)
        at 
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
        at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
        at java.lang.Thread.run(Thread.java:619)
Caused by: org.apache.rampart.RampartException: Error in extracting message 
properties
        at 
org.apache.rampart.RampartMessageData.<init>(RampartMessageData.java:290)
        at org.apache.rampart.MessageBuilder.build(MessageBuilder.java:58)
        at 
org.apache.rampart.handler.RampartSender.invoke(RampartSender.java:64)
        ... 12 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:157)
        at 
org.apache.rampart.RampartMessageData.<init>(RampartMessageData.java:150)
        ... 14 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:107)
        ... 15 more

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to