Thank you for pointing this out. On review, our package naming isn't terribly conducive to use within OSGi it seems. We have started to make the appropriate changes in our jetty-9[1] branch as a direct result of your question.
So far websocket has been corrected [2], and the SPDY correction is underway. Note however, that we cannot make this kind of change in jetty-7 or jetty-8 as it would represent too big of a change for a point release. [1] http://git.eclipse.org/c/jetty/org.eclipse.jetty.project.git/log/?h=jetty-9 [2] http://git.eclipse.org/c/jetty/org.eclipse.jetty.project.git/commit/?h=jetty-9&id=b10a10797d88728a3ef5206c77dbe7821dae2bb5 -- Joakim Erdfelt <[email protected]> www.webtide.com Developer advice, services and support from the Jetty & CometD experts. On Mon, Sep 17, 2012 at 8:15 PM, Guofeng Zhang <[email protected]> wrote: > Hi,**** > > ** ** > > These days I learning how Jetty support SPDY. I found that spdy-core and > spdy-jetty use the same package name. the SPDY modules and npn module has > no OSGi headers defined.**** > > ** ** > > My question is:**** > > will these modules support OSGi in the future, and if so, is there not > any issue for the split package in the OSGi environment?**** > > ** ** > > Thanks,**** > > ** ** > > Guofeng**** > > ** ** > > _______________________________________________ > jetty-users mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/jetty-users > >
_______________________________________________ jetty-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/jetty-users
