Re: [CXF2.2.3] On exception handling

2009-08-14 Thread Sergey Beryozkin
heckResultObject(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 > >

Re: [CXF2.2.3] On exception handling

2009-08-12 Thread Gabo Manuel
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.cx

Re: [CXF2.2.3] On exception handling

2009-08-12 Thread Sergey Beryozkin
e same except for the test scenario that I encountered. In > testGetBook123, try using > > http://localhost:9080/webapp/bookstore/nonexistent/ > > > Do I need to have that setToHandle in the mapper implementation class? > > Thanks, > > Gabo > > -- View this message in context: http://www.nabble.com/-CXF2.2.3--On-exception-handling-tp24859798p24931888.html Sent from the cxf-user mailing list archive at Nabble.com.

Re: [CXF2.2.3] On exception handling

2009-08-11 Thread Gabo Manuel
Hi Sergey, Sergey Beryozkin wrote: Hi Gabo I'm wondering, how I can reproduce it... I have two exception mappers in the system tests area, the first one catching an application exception, the second one a spring security exception. I've tried updating the status code in [1] from 500 to 401 a

Re: [CXF2.2.3] On exception handling

2009-08-11 Thread Sergey Beryozkin
ception causes the status to be 500 but the message is not >>> included in the body. Also, there are times that I would want the status >>> to be 400 but with the exception, the status is fixed at 500. >>> >>> Please advise. >>> >>> Gabo >>> >>> >>> >>> >> >> >> >> >> >> No virus found in this incoming message. >> Checked by AVG - www.avg.com >> Version: 8.5.392 / Virus Database: 270.13.45/2287 - Release Date: >> 08/07/09 06:22:00 >> >> > > -- View this message in context: http://www.nabble.com/-CXF2.2.3--On-exception-handling-tp24859798p24918194.html Sent from the cxf-user mailing list archive at Nabble.com.

Re: [CXF2.2.3] On exception handling

2009-08-07 Thread Gabo Manuel
Hi Sergey, I am expecting it to handle RuntimeException from the code and from the framework. So far, my test includes both from the method and that of no resource mapping to the url provided, e.g. "/Service/nonexistent" instead of "/Service/operation" Thanks. Gabo Sergey Beryozkin wrote:

Re: [CXF2.2.3] On exception handling

2009-08-07 Thread Sergey Beryozkin
so, there are times that I would want the status > to be 400 but with the exception, the status is fixed at 500. > > Please advise. > > Gabo > > > -- View this message in context: http://www.nabble.com/-CXF2.2.3--On-exception-handling-tp24859798p24862076.html Sent from the cxf-user mailing list archive at Nabble.com.

[CXF2.2.3] On exception handling

2009-08-06 Thread Gabo Manuel
Hi All, I created and registered an ExceptionMapper implementation as follows: public class RuntimeExceptionMapper implements ExceptionMapper{ private static Logger logger = Logger.getLogger(RuntimeExceptionMapper.class); public Response toResponse(RuntimeException fault) { lo