How can I prevent Apache CXF from sending a response message?

I've been able to do this with an interceptor that aborts the interceptor chain.

I've been able to do this with an interceptor that aborts the interceptor chain. I've tested this with an HTTP config (WebSphere returns an empty 200) and an ActiveMQ config (no response comes back to the response queue). Package my.super.

Interceptor; public final class Suppressor extends AbstractSoapInterceptor { public Suppressor() { super(Phase. SETUP); } @Override public void handleMessage(final SoapMessage message) throws Fault { final boolean suppressResponse = this. SuppressResponse(message); if(suppressResponse) { log.

Debug("-> Suppressing response"); message. GetInterceptorChain().abort(); } //if you want to suppress both responses and faults, you need //to check them separately. //Change this code to check headers for whatever criteria you want //(Note you may need to change the super(Phase...) ) //The code's a bit messy here - just sketching out the idea for the answer private boolean suppressResponse(final Message message) { final Fault fault = (Fault)message.

GetContent(Exception. Class); if(fault! = null) { final String faultMessage = fault.getMessage(); return faultMessage.

IndexOf("Something-you-want-to-match") > 0; } else { final MessageInfo messageInfo = (MessageInfo)message. Get("org.apache.cxf.service.model. MessageInfo"); final String operation = messageInfo.getOperation().getOutputName(); return operation.

IndexOf("Something-you-want-to-match") > 0; } } and your applicationContext.xml.

Long explanation: think about SOAP web services in terms of SOAP protocol specification. Web services is not just a fancy layer on top of HTTP, it is actually a way to describe two-way communication with various message exchange patterns implemented. The following patterns are most common ones: request-response (In-Out): in HTTP environment this is a typical HTTP request/response call with some request message being sent from client to server and some response message is sent back.In JMS environment you would get two separate and independent messages.

One-way (In-Only): in this model the client send a request but does not expect nor care about the response. In JMS it is equivalent to a simple message sent to the broker.In HTTP on the other hand (at least this is how one-way methods are implemented in Apache CXF) you will get a void method on SEI. Moreover, CXF by default will use a separate thread pool to handle this request, so the client doesn't even wait for the response and the server is not even able to send that response (because the client might have already disconnected).

Now the important part: in WSDL you either define a method as request/response (by defining in/out messages) or as one-way (by only providing in message). This is fixed in service contract. You cannot make a method that once returns response (out message to be precise) while other times it does not.

Obviously you can define an out message that can be empty or contain some content, but you still have to return something. Short explanation: SOAP protocol is not flexible enough to fulfil your requirement. You either return a response or not.

Create two methods and choose which one to call on the client side rather than adding custom headers. Another tip: you might use ESB to perform some sort of transformation so that the response is discarded in presence of some SOAP header.

I thought about using duplicate operation definitions (a request-response definition and a one-way definition), but this doesn't scale well to tens or hundreds of services (it doubles the number of services you must implement). – Jared Sep 27 at 21:59 I also considered the ESB-based solution, but the whole point is to remove the added overhead of publishing the response. I would still be pushing responses into the ESB layer only to discard them.

– Jared Sep 27 at 22:00.

For your particular scenario I think the correct way to implement is to use two operations. One for in-only and other for in-out. The way you try to implement it may cause problems in client side as well.

Now client has to decide whether to look for a response or not depending on the request. On the other hand since the decision is taken from a value send by the client at the client side it can decide to invoke the in-only or in-out operation.

Jared: I am mostly agreed with Tomasz's explanation. One workaround I can think of lets say if use ws-addressing. Ws-addressing allows you to specify and .

So basically, in scenario you don't want response to be sent to client who has requested, server side code can alter the value of replyTo field and can send response to dummy URI.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.