[ 
http://issues.apache.org/jira/browse/AXIS2-1135?page=comments#action_12434056 ] 
            
Ruchith Udayanga Fernando commented on AXIS2-1135:
--------------------------------------------------

We need further improvements to fix the AXIOM issue:

http://issues.apache.org/jira/browse/WSCOMMONS-90#action_12434046
http://issues.apache.org/jira/browse/WSCOMMONS-90#action_12434055

Then we will be able to fix this issue.

Thanks,
Ruchith

> ClassCastException in AddressingOutHandler when Rahas is engaged
> ----------------------------------------------------------------
>
>                 Key: AXIS2-1135
>                 URL: http://issues.apache.org/jira/browse/AXIS2-1135
>             Project: Apache Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: Addressing
>            Reporter: Mario A. Rodriguez
>         Assigned To: Eran Chinthaka
>
> I'm trying to figure out how to configure/use Rahas for WS-SecConv 
> interactions. However, my service is failing in the MessageOut phase.
> I am receiving the following exception: (some line numbers may not match due 
> some extra logging that I've added)
> Caused by: java.lang.ClassCastException: 
> org.apache.axiom.om.impl.llom.OMElementImpl
>       at org.apache.axiom.om.impl.dom.ParentNode.addChild(ParentNode.java:56)
>       at 
> org.apache.axis2.handlers.addressing.AddressingOutHandler.processReferenceInformation(AddressingOutHandler.java:364)
>       at 
> org.apache.axis2.handlers.addressing.AddressingOutHandler.addToSOAPHeader(AddressingOutHandler.java:314)
>       at 
> org.apache.axis2.handlers.addressing.AddressingOutHandler.processReplyTo(AddressingOutHandler.java:254)
>       at 
> org.apache.axis2.handlers.addressing.AddressingOutHandler.invoke(AddressingOutHandler.java:125)
> The line in question is attempting to do:                 
>         OMElement omElement = (OMElement) referenceInformation.get(key);
>          parent.addChild(omElement);   <--- exception occurs inside this call 
> when addChild() attempts to cast omElement to Node.
> According to the Axis2 trace logs, the RequestSecurityToken request was 
> handled successfully by Rahas, but it then gets hung up while writing the 
> addressing headers to the response. The addressing module appears to work 
> correctly if Rahas is not engaged.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to