That's what I thought, until I opened up that class and saw it was 127 lines and a decent amount of code. But, on closer examination, the majority of appears to be about logging (which I do already), customizing error message (which I don't care about), and working around broken implementations that return null from getResponse (does this happen practically?).
So, in conclusion, I'll keep the delegation to CXF internal class for now but note that if we switch from CXF or the code becomes incompatible with a future CXF release, just return getResponse, it's portable and good enough. Thanks, Jason > -----Original Message----- > From: Sergey Beryozkin [mailto:[email protected]] > Sent: Friday, December 13, 2013 11:23 AM > > I guess the most portable way is to convert this caught > WebApplicationException into response, simply return > caughtWebApplicationException.getResponse() from your catch-all mapper > > Cheers. Sergey ---------------------------------------------------------------------- This email message and any attachments are for the sole use of the intended recipient(s). Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message and any attachments.
