Hi Vrignaud,
I can reproduce a bug. Will work on it.
Thank you for great bug report.
Could you create issue for it on
https://grizzly.dev.java.net/issues/ ?
Thank you again,
Hubert
On Wed, May 13, 2009 at 3:39 PM, Vrignaud Etienne <evrignaud_at_axway.com>wrote:
> Hi,
>
>
>
> I am trying to use the Felix Web Console with the HttpService
> implementation provided by the new Grizzly HttpService.
>
> I read some information on
> http://codemeself.blogspot.com/2009/03/grizzly-osgi-http-service-guide.html
>
> And after I tried to setup myself a standalone test bed to check that new
> stuff. I am very interest to use it in my application.
>
> For that test bed, I peek the last Felix 1.6.1 archive and added all the
> mandatory bundles in order to get the WebConsole and grizzly-httpservice
> install well. Unfortunately the WebConsole servlet doesn’t work.
>
> And I am in trouble to figure out what going on with that problem.
>
>
>
> To help finding solution, I have setup also a concurrent solution that use
> the Pax Web bundle (http://wiki.ops4j.org/display/paxweb/Pax+Web). And in
> that case, everything is ok.
>
>
>
> This solution doesn’t feet to my needs as it use Jetty as Http Connector.
>
> In my case, the Http connector is Grizzly.
>
> So I am very interest in finding a solution to that problem.
>
>
>
> I put in attachement the test bed that I have made.
>
> To start each one, just go into with-grizzly-httpservice or with-pax-web.
>
> And type
>
> java -jar bin/felix.jar
>
>
>
> Regards,
>
> Etienne VRIGNAUD
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_grizzly.dev.java.net
> For additional commands, e-mail: users-help_at_grizzly.dev.java.net
>