cxf-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sergey Beryozkin <sberyoz...@gmail.com>
Subject Re: JAX-RS Interrupt StreamingOutput
Date Mon, 16 Oct 2017 09:14:46 GMT
Hi,

How does the JAX-RS server code react when it sees some issue, does it 
throw some exception ?

Sergey
On 16/10/17 10:05, MULLER, Anthony wrote:
> Hi Sergey,
> 
> Thank you very much for your reply!
> 
> The point here is that the client isn't a Java application, but a Web browser for instance
(like Chrome).
> 
> Best regards,
> Anthony
> 
> -----Original Message-----
> From: Sergey Beryozkin [mailto:sberyozkin@gmail.com]
> Sent: lundi 16 octobre 2017 10:38
> To: users@cxf.apache.org
> Subject: Re: JAX-RS Interrupt StreamingOutput
> 
> Hi Anthony
> 
> AFAIK the status goes first with the 1st write, so there's really no way
> to replace it with something else if there was an error later on while
> writing the stream.
> 
> I don't think so the fact a client gets 200 and then, presumably,
> IOException, is inconsistent, the client code reading the data directly
> from the input stream always has a catch for IOException, it can be
> thrown even if there were no errors on the server side when writing it...
> 
> Sergey
> 
> 
> On 13/10/17 12:30, MULLER, Anthony wrote:
>> Hello,
>>
>> I have a REST call which returns a generated ZIP output. But during generation, an
issue may occurred... However, the client seems to receive a HTTP code 200 with a corrupted
ZIP.
>>
>> Is it possible to do better? Is this case managed by HTTP protocol? By CXF?
>>
>> Best regards,
>> Anthony
>>

Mime
View raw message