I’m scratching my head over this:
Using an Interceptor to check a few SOAP headers, how can I abort the interceptor chain but still respond with an error to the user?
Throwing a Fault works regarding the output, but the request is still being processed and I’d rather not have all services check for some flag in the message context.
Aborting with “message.getInterceptorChain().abort();” really aborts all processing, but then there’s also nothing returned to the client.
What’s the right way to go?
public class HeadersInterceptor extends AbstractSoapInterceptor {
public HeadersInterceptor() {
super(Phase.PRE_LOGICAL);
}
@Override
public void handleMessage(SoapMessage message) throws Fault {
Exchange exchange = message.getExchange();
BindingOperationInfo bop = exchange.getBindingOperationInfo();
Method action = ((MethodDispatcher) exchange.get(Service.class)
.get(MethodDispatcher.class.getName())).getMethod(bop);
if (action.isAnnotationPresent(NeedsHeaders.class)
&& !headersPresent(message)) {
Fault fault = new Fault(new Exception("No headers Exception"));
fault.setFaultCode(new QName("Client"));
try {
Document doc = DocumentBuilderFactory.newInstance()
.newDocumentBuilder().newDocument();
Element detail = doc.createElementNS(Soap12.SOAP_NAMESPACE, "mynamespace");
detail.setTextContent("Missing some headers...blah");
fault.setDetail(detail);
} catch (ParserConfigurationException e) {
}
// bad: message.getInterceptorChain().abort();
throw fault;
}
}
}
Following the suggestion by Donal Fellows I’m adding an answer to my question.
CXF heavily relies on Spring’s AOP which can cause problems of all sorts, at least here it did. I’m providing the complete code for you. Using open source projects I think it’s just fair to provide my own few lines of code for anyone who might decide not to use WS-Security (I’m expecting my services to run on SSL only). I wrote most of it by browsing the CXF sources.
Please, comment if you think there’s a better approach.
As mentioned above, here’s the ExceptionHandler/-Logger. At first I wasn’t able to use it in combination with JAX-RS (also via CXF, JAX-WS works fine now). I don’t need JAX-RS anyway, so that problem is gone now.