Re: What is the proper way of implementing try/catch semantics using CXF Interceptors?

itself to use Java's try/catch syntax. What is the proper way of implementing try/catch semantics using CXF Interceptors on a Client? What we currently do: 1) We're adding a QosBeforeInterceptor early in the Client's out interceptor chain. This implements handleMessage. We increment

Re: What is the proper way of implementing try/catch semantics using CXF Interceptors?

); } chain.doFilter(request, response); } finally { counter.decrementAndGet(); } However, CXF's interceptor design doesn't lend itself to use Java's try/catch syntax. What is the proper way of implementing try/catch semantics using CXF Interceptors on a Client? What we

Re: What is the proper way of implementing try/catch semantics using CXF Interceptors?

try/catch semantics using CXF Interceptors on a Client? What we currently do: 1) We're adding a QosBeforeInterceptor early in the Client's out interceptor chain. This implements handleMessage. We increment the counter. If it is larger than N we throw a SoapFault. In this case handleFault gets

What is the proper way of implementing try/catch semantics using CXF Interceptors?

lend itself to use Java's try/catch syntax. What is the proper way of implementing try/catch semantics using CXF Interceptors on a Client? What we currently do: 1) We're adding a QosBeforeInterceptor early in the Client's out interceptor chain. This implements handleMessage. We increment