Hi Gabo There's absolutely no need to apologize :-) It's good we've verified that no custom status code is being lost, when set in custom exception mappers.
I'm not sure yet about default WebApplicationExceptionMapper reporting error messages too, in addition to 500. I may need to check the spec, but I don't remember anything specific...You might want to register your own WebApplicationExceptionMapper, it will work well with your custom RuntimeExceptionMapper cheers, Sergey Gabo Manuel wrote: > > Hi Sergey, > > Sorry to have bothered you. This is all just one big stupid mistake on > my part. I specifically set the code to 400, even if I was thinking 500 > at that time. Terribly sorry about this. > > (To somehow redeem myself) I just noticed this in the logs: > > Aug 13, 2009 6:30:12 AM org.apache.cxf.jaxrs.JAXRSInvoker > checkResultObject > INFO: Null subresource locator is returned for path /nonexistent/ > 2009-08-13 06:30:12,703 | [FATAL][80-1][ RuntimeExceptionMapper] > | Issue #200922560001 > javax.ws.rs.WebApplicationException > at > org.apache.cxf.jaxrs.JAXRSInvoker.checkResultObject(JAXRSInvoker.java:239) > > Would it be possible to include "Null subresource locator is returned > for path /nonexistent/" as part of the error messsage? Currently, I am > getting an empty message. > > Again, my apologies. > > Gabo > > -- View this message in context: http://www.nabble.com/-CXF2.2.3--On-exception-handling-tp24859798p24970288.html Sent from the cxf-user mailing list archive at Nabble.com.
