Hubert Iwaniuk wrote:
>
> 1. I don't know how to do it in Eclipse. But if you clone gitorial you
> just
> need to change <framework> in pom.xml from felix to equinox and do mvn
> install pax:provision.
>
Unfortunately we're not using Maven here (yeah, I know, it's bad...) and btw
I don't know anything to Maven. So what I'm trying to do is basically
installing the bundle jar into Equinox by wrapping it inside an eclipse
plugin. At first I thought I could embed it as is, but it seems a little bit
more trickier (I have created the bundle, run it, it seems installed as it
appears as RESOLVED when I ask for its status, but I have nobody listening
on the http port nor on port 8080). Perhaps I must start the webserver
manually in the plugin activator ? I thought it was already done.
Hubert Iwaniuk wrote:
>
> 2. I'm having problems understanding problem here, could you elaborate a
> bit
> more on what you want to achieve with grizzly and jetty connector.
>
> OSGi Http Service is all that you get from Grizzlys OSGi implementation,
> though Grizzly supports nearly full Servlet spec.
>
It seems that both the Grizzly OSGi bundle AND the jetty equinox bundle
provide the Http Service, so I guess there is a clash here.
So my idea is to re-use the jetty equinox bundle, and package the
jetty-grizzly connector and the grizzly framework in another plugin. I hope
that doing this I would be able to develop other plugins that register GWT
Comet servlets using support from grizzly. But I'm not sure what's the
proper way to do this.
Is it a bit more clear ?
Vincent
--
View this message in context: http://www.nabble.com/Grizzly-%2B-Equinox-OSGi-%2B-Eclipse-tp22702068p22705367.html
Sent from the Grizzly - Users mailing list archive at Nabble.com.