You're welcome.Fixing bugs with this kind of bug reports is fun :)
Hubert
On Fri, Mar 27, 2009 at 4:16 PM, Paul Sandoz <Paul.Sandoz_at_sun.com> wrote:
> On Mar 27, 2009, at 4:12 PM, Hubert Iwaniuk wrote:
>
> Fix in trunk.
>
>
> Thanks, very fast!
> Paul.
>
> Thanks again for great bug report.
>
> Cheers,
> Hubert
>
>
> On Fri, Mar 27, 2009 at 3:08 PM, Hubert Iwaniuk <neotyk_at_kungfoo.pl> wrote:
>
>> Hi Paul,
>> Great bug report :)
>> Ticket: https://grizzly.dev.java.net/issues/show_bug.cgi?id=499
>> Fix soon to be available in trunk.
>>
>> Cheers,
>> Hubert.
>>
>>
>> On Fri, Mar 27, 2009 at 10:22 AM, Paul Sandoz <Paul.Sandoz_at_sun.com>wrote:
>>
>>> Hi,
>>>
>>> When using Grizzly 1.9.8 and 1.9.9-SNAPSHOT i noticed when i set up the
>>> GrizzlyWebServer to use a filter that the Filter.destroy method is not
>>> called when i stop of the GrizzlyWebServer e.g.
>>>
>>> GrizzlyWebServer ws = new GrizzlyWebServer(port);
>>>
>>> ServletAdapter sa = new ServletAdapter();
>>>
>>> sa.addFilter(new MyFilter(), "filter", null);
>>>
>>> sa.setContextPath(baseUri.getRawPath());
>>>
>>> ws.addGrizzlyAdapter(sa, new String[] {""} );
>>>
>>> ws.start();
>>>
>>> // Do some stuff...
>>>
>>> ws.stop() // MyFilter.destroy() not called
>>>
>>> Attached is a simple maven project that reproduces the issue. See the
>>> filter.Main.MyFilter class, which should print something out on destroy.
>>>
>>> Paul.
>>>
>>>
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe_at_grizzly.dev.java.net
>>> For additional commands, e-mail: users-help_at_grizzly.dev.java.net
>>>
>>
>>
>
>