axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ruchith Udayanga Fernando (JIRA)" <>
Subject [jira] Commented: (AXIS2-1135) ClassCastException in AddressingOutHandler when Rahas is engaged
Date Mon, 11 Sep 2006 12:54:22 GMT
    [ ] 
Ruchith Udayanga Fernando commented on AXIS2-1135:

Created a feature improvement in AXIOM  to add method to import an OM node :

When this is fixed we can fix this issue by importing nodes before adding them into the new
OM structure.


> ClassCastException in AddressingOutHandler when Rahas is engaged
> ----------------------------------------------------------------
>                 Key: AXIS2-1135
>                 URL:
>             Project: Apache Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: Addressing
>            Reporter: Mario A. Rodriguez
> 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:
> 	at
> 	at org.apache.axis2.handlers.addressing.AddressingOutHandler.processReferenceInformation(
> 	at org.apache.axis2.handlers.addressing.AddressingOutHandler.addToSOAPHeader(
> 	at org.apache.axis2.handlers.addressing.AddressingOutHandler.processReplyTo(
> 	at org.apache.axis2.handlers.addressing.AddressingOutHandler.invoke(
> 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:
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message