Hi,

I created a jira issue for this but perhaps i'm wrong and should've posted
here first so i apologize for that.

the issue i'm seeing is that the current findExceptionMapper in
ClientProxyImpl
seems to go by getting the exceptions in the throws signature of the method
and once it
finds a mapper for the first Exception listed it will use this
even if the exceptions don't match

so say i have
myMethod() throws Exception1, Exception2;
 with corresponding server/client exception to response and from mappers.

now in the method i throw Exception2

based on the current findExceptionMapper it will pick up the response mapper
for 
Exception1 on client side even if i have a Exception2ResponseMapper also
registered and want to use that..

reordering them will pick the right one for just that situation but suppose
we throw Exception1 in there in some other branch of the method.. now it
picks Exception2ResponseMapper if 
our signature is
myMethod() throws Exception2, Exception1;

is there a workaround for this?

the jira issue is here with deails of my classes and even a zip file with
full setup 
of mappers/exception and server/client test:
https://issues.apache.org/jira/browse/CXF-4912



--
View this message in context: 
http://cxf.547215.n5.nabble.com/cxf-rest-client-always-picks-the-first-ResponseExceptionMapper-for-a-method-with-different-exceptions-tp5725071.html
Sent from the cxf-user mailing list archive at Nabble.com.

Reply via email to