Hi, Currently ClientProxyImpl selects exactly one response exception mapper. Selection is based on exceptions declared in business method and generic parameter of response exception mapper (ClientProxyImpl.findExceptionMapper(), ClientProviderFactory. createResponseExceptionMapper(), ProviderFactory.handleMapper()). Chain of response exception mappers is not supported.
Not sure how many use cases require multiple response exception mappers for single method, but basically it can be supported as well. Regards, Andrei. > -----Original Message----- > From: parwiz [mailto:[email protected]] > Sent: Samstag, 23. März 2013 09:21 > To: [email protected] > Subject: Re: cxf rest client always picks the first ResponseExceptionMapper > for a method with different exception throws > > maybe perhaps add a header in response when a fault occurs and have the > fully qualified name of the exception in there.. and then in our client side > findExceptionMapper we can first use this header and see if a mapper exists > for it or a super class of it.. > if yes use that else fall back on the current method of going by > Method.getExceptionTypes()? > > please let me know because right now this is cause us some issues.. > > and no I can't simply extend both Exception1 and Exception2 from same > parent and handle them that way... one is a legacy exception (external > source/3rd > party) and one is a newer exception from our own code > > > > -- > 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-tp5725071p5725072.html > Sent from the cxf-user mailing list archive at Nabble.com.
