cxf-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Beilin, Vadim" <>
Subject ReadHeadersInterceptor requires element prefix?
Date Thu, 10 Sep 2015 17:39:47 GMT
We are moving one of our projects from CXF 2.7.12 to 2.7.16.
A number of tests are failing with exceptions like the following:

java.lang.IllegalArgumentException: prefix cannot be "null" when creating a QName
                at javax.xml.namespace.QName.<init>( ~[na:1.7.0_67]
                at org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor$HeadersProcessor.process(
                at org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor.handleMessage(
                at org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor.handleMessage(
                at org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(
                at org.apache.cxf.transport.ChainInitiationObserver.onMessage(

The message being sent looks like
                <Envelope xmlns=""><Body>.....

It looks like ReadHeadersInterceptor.HeadersProcessor expects the elements (Envelope, Header)
to have a prefix.
I can't find any requirement to this effect (that the SOAP namespace should not be a default
namespace) in soap specs.

Am I missing something here, or is it a regression in ReadHeadersInterceptor?



NOTICE: Morgan Stanley is not acting as a municipal advisor and the opinions or views contained
herein are not intended to be, and do not constitute, advice within the meaning of Section
975 of the Dodd-Frank Wall Street Reform and Consumer Protection Act. If you have received
this communication in error, please destroy all electronic and paper copies; do not disclose,
use or act upon the information; and notify the sender immediately. Mistransmission is not
intended to waive confidentiality or privilege. Morgan Stanley reserves the right, to the
extent permitted under applicable law, to monitor electronic communications. This message
is subject to terms available at the following link:
If you cannot access these links, please notify us by reply message and we will send the contents
to you. By messaging with Morgan Stanley you consent to the foregoing.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message