0

I am using Apache CXF 4.1.3, the latest version. I have an implementation of a jakarta.xml.ws.Provider<T> interface where my invoke function sometimes needs to return an error.

According to the JavaDoc of Provider.invoke:

@throws WebServiceException If there is an error processing request. The cause of the {@code WebServiceException} may be set to a subclass of {@code ProtocolException} to control the protocol level representation of the exception.

In my case, my protocol used is HTTP, so I implement this in case of any error:

throw new WebServiceException("something went wrong", new HttpException(123))

to test whether the specific HTTP status code 123 (an example!) is actually used. It's not.

No matter what I do, the HTTP status code is always 500.

How can I persuade this interface to function as documented?

Improve this question
Related questions
7
JAX-RS response with HTTP status 500 instead of HTTP status 400
0
How to override the cxf MessageSenderEndingInterceptor and take control over handleMessage method
4
How to set the HTTP STATUS code to other than 500 in CXF Out Fault Interceptor?
Load 5 more related questions Show fewer related questions

0

Reset to default

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.