Ah yeah. I'm just assuming that anything not specifically handled in
my code's error handling or under the umbrella of
WebApplicationException is going to be some kind of unexpected server
error so I will probably map them to a 500.
On Tue, Feb 2, 2010 at 11:27 AM, Robert Koberg <rob_at_koberg.com> wrote:
>
> On Feb 2, 2010, at 11:13 AM, Chris Carrier wrote:
>
>> The WebApplicationException contains the status. Something like:
>>
>> e.getResponse().getStatus()
>
>
> Sorry, I meant with the Throwable, rather than the WebApplicationException
>
> -Rob
>
>
>>
>> Chris
>>
>> On Tue, Feb 2, 2010 at 11:08 AM, Robert Koberg <rob_at_koberg.com> wrote:
>>>
>>> On Feb 2, 2010, at 10:23 AM, Paul Sandoz wrote:
>>>>
>>>> For any complete solution you will need to check the status code and if any entity exists for e as your application may, in the future say, throw a WebApplicationException or an extension of.
>>>
>>> How would you get the status code?
>>>
>>> -Rob
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe_at_jersey.dev.java.net
>>> For additional commands, e-mail: users-help_at_jersey.dev.java.net
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe_at_jersey.dev.java.net
>> For additional commands, e-mail: users-help_at_jersey.dev.java.net
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_jersey.dev.java.net
> For additional commands, e-mail: users-help_at_jersey.dev.java.net
>
>