dev@grizzly.java.net

Re: DefaultProtocolChain bug?

From: Jeanfrancois Arcand <Jeanfrancois.Arcand_at_Sun.COM>
Date: Wed, 09 Jan 2008 11:37:06 -0500

Hi,

Oleksiy Stashok wrote:
> Hi,
>
> once we will have this fix, we need to integrate new version of Grizzly
> to Sailfin.
> As this bug is critical for Sailfin.

Or extends the class in Sailfin to add the fix, as the next version for
Sailfin is 1.7.0 (we shouldn't release anything new just for that bug,
right?)

Thanks

-- Jeanfrancois


>
> Thank you.
>
> WBR,
> Alexey.
>
> Jeanfrancois Arcand wrote:
>> Salut,
>>
>> +1
>>
>> -- Jeanfrancois
>>
>> Oleksiy Stashok wrote:
>>> Hello,
>>>
>>> when investigating one of the Sailfin issue, I found that current
>>> DefaultProtocolChain exception control could be improved.
>>> Think we should catch *all* types of Exceptions on execution phase
>>> and call postExecute on all filters, which were passed before
>>> exception happened.
>>>
>>> Here is proposed fix attached.
>>>
>>> Thanks.
>>>
>>> WBR,
>>> Alexey.
>>>
>>>
>>> ------------------------------------------------------------------------
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe_at_grizzly.dev.java.net
>>> For additional commands, e-mail: dev-help_at_grizzly.dev.java.net
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe_at_grizzly.dev.java.net
>> For additional commands, e-mail: dev-help_at_grizzly.dev.java.net
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe_at_grizzly.dev.java.net
> For additional commands, e-mail: dev-help_at_grizzly.dev.java.net
>