users@jax-rs-spec.java.net

[jax-rs-spec users] [jsr339-experts] Re: Re: Re: Re: Re: Re: Re: Re: Re: Concerns about the client-side exception hierarchy

From: Bill Burke <bburke_at_redhat.com>
Date: Fri, 30 Mar 2012 06:18:34 -0400

On 3/30/12 5:31 AM, Sergey Beryozkin wrote:
> Hi Bill
> On 29/03/12 16:26, Bill Burke wrote:
>> You could punt on server-side exceptions and just have a client
>> hierarchy. (If we went the ClientResponse route).
>>
> I guess it would be the only option in this case as far as the
> introduction of child (server) exceptions is concerned, I'm however
> becoming 'fond' of your original idea of the app developer being able to
> 'throw new BadClientRequestException()'. I think if we can not reuse
> such exception then at this stage we should punt on all the child
> exceptions and simply refactor a bit the current client-side hierarchy
> as was suggested originally and review the idea in post 2.0
>

Ya, I'm fond of it too. It works really nice in practice. I just know
we'll have some lame 'Spring-JAXRS" project that will do just this...

BTW, I still think ClientResponse extending Response would solve the
problem.

Bill

-- 
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com