I am in the process of developing a client for a systinet web service, which
is very picky about how the SOAP message is formed.
Using a SOAPHandler I have successfully formatted the message as it needs to
be sent and at the end of the handler chain output the message to a log
file. However, upon being processed by one of the interceptors during the
WRITE phase, the message is reprocessed and loses some of it's namespace
declarations. In the example below you will see that the "wsa" namespace is
preserved but the "wsu" namespace is removed even though both are being
used. The server then complains that "wsu" is unbound.
Anyone understand why this is happening? Is there anyway to prevent this
from occurring?
Any help you can give would be appreciated!
i.e.
Message After Handlers but before Standard Interceptors
...
<wsa:MessageID
xmlns:wsa="http://schemas.xmlsoap.org/ws/2003/03/addressing";
xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd";
wsu:Id="id-2342342" soap:mustUnderstand="0">
ID_5706234234234234234234234
</wsa:MessageID>
...
Message Sent/Logged after Standard Interceptors
...
<wsa:MessageID
xmlns:wsa="http://schemas.xmlsoap.org/ws/2003/03/addressing";
wsu:Id="id-2342342" soap:mustUnderstand="0" soap:actor="">
ID_5706234234234234234234234
</wsa:MessageID>
...
--
View this message in context:
http://www.nabble.com/Handler--%3E-Interceptor-Namespace-Removal-tp19805539p19805539.html
Sent from the cxf-user mailing list archive at Nabble.com.
