Hi Oliver, Technically, you could write an interceptor that extends the TransformOutInterceptor and in its handleMessage method, remove the exception from the message, call super.handleMethod and reinsert the exception. And let the standard soap fault interceptor serialize the fault/exception over the transform out filter. I think this would work.
But I think it could probably make more sense to even skip this check in TransformOutInterceptor's handle method or at least to provide an option to skip this check in there so that you don't need that kind of construction. regards, aki 2013/1/14 Oliver Moser <[email protected]>: > Hi all > > I'm trying to transform a namespace in a SoapFault. At first glance, the > StaxTransformFeature or the TransformOutInterceptor (which can be configured > in the <outFaultInterceptors> list) looked promising. After playing around a > bit, I realized that the TransformOutInterceptor might not be intended to > transform the content of a SoapFault. In my understanding, the > handleMessage() method prohibits this by the following line > > // org.apache.cxf.interceptor.transform.TransformOutInterceptor#handleFault > if (null != message.getContent(Exception.class)) { > return; > } > > Is there an alternative approach that allows to transform namespaces in > SoapFault messages? > > cheers > > > -- > Oliver Moser > http://www.omoser.com >
