It looks like the ‘org.eclipse.jetty.websocket.server' and ‘org.eclipse.jetty.websocket.servlet’ bundles have bad headers in their manifests. They both declare a Require-Capability in the osgi.extender namespace which is effective at resolve time. Bundles should never require anything from the osgi.extender namespace merely in order to resolve.
To proceed, you would have to find whatever bundle provides the “osgi.extender=osgi.serviceloader.processor” capability. I don’t know what bundle that might be. The Jetty developers *should* know… assuming they even tested their bundles before releasing them! Neil > On 29 Oct 2015, at 13:05, i...@cuhka.com wrote: > > I've copied the jars that Jetty mentions into felix's bundle folder. I've > also copied the jars under the websocket folder into felix's bundle folder. > > Two Websocket bundles don't resolve, but this is due to an OSGi service > loader bundle? Which bundle should I install? > > > g! start 127 > org.osgi.framework.BundleException: Unable to resolve > org.eclipse.jetty.websocket.server [127](R 127.0): missing requirement > [org.eclipse.jetty.websocket.server [127](R 127.0)] osgi.extender; > (osgi.extender=osgi.serviceloader.registrar) Unresolved requirements: > [[org.eclipse.jetty.websocket.server [127](R 127.0)] osgi.extender; > (osgi.extender=osgi.serviceloader.registrar)] > > g! start 128 > org.osgi.framework.BundleException: Unable to resolve > org.eclipse.jetty.websocket.servlet [128](R 128.0): missing requirement > [org.eclipse.jetty.websocket.servlet [128](R 128.0)] osgi.extender; > (osgi.extender=osgi.serviceloader.processor) Unresolved requirements: > [[org.eclipse.jetty.websocket.servlet [128](R 128.0)] osgi.extender; > (osgi.extender=osgi.serviceloader.processor)] > > > > 109|Active | 1|Jetty :: Deployers (9.3.5.v20151012) > 110|Active | 1|Jetty :: Http Utility (9.3.5.v20151012) > 111|Active | 1|Jetty :: IO Utility (9.3.5.v20151012) > 112|Active | 1|Jetty Servlet API and Schemas for OSGi (3.1.0.M3) > 113|Active | 1|Jetty :: Security (9.3.5.v20151012) > 114|Active | 1|Jetty :: Server Core (9.3.5.v20151012) > 115|Active | 1|Jetty :: Utilities (9.3.5.v20151012) > 116|Active | 1|Jetty :: Webapp Application Support (9.3.5.v20151012) > 117|Active | 1|Jetty :: XML utilities (9.3.5.v20151012) > 118|Active | 1|ASM (5.0.1) > 119|Installed | 1|ASM commons classes (5.0.1) > 120|Active | 1|Jetty :: Websocket :: javax.websocket :: Client > Implementation (9.3.5.v20151012) > 121|Installed | 1|Jetty :: Websocket :: javax.websocket.server :: Server > Implementation (9.3.5.v20151012) > 122|Active | 1|javax.annotation API (1.2.0) > 123|Active | 1|WebSocket server API (1.0.0) > 124|Active | 1|Jetty :: Websocket :: API (9.3.5.v20151012) > 125|Active | 1|Jetty :: Websocket :: Client (9.3.5.v20151012) > 126|Active | 1|Jetty :: Websocket :: Common (9.3.5.v20151012) > 127|Installed | 1|Jetty :: Websocket :: Server (9.3.5.v20151012) > 128|Installed | 1|Jetty :: Websocket :: Servlet Interface > (9.3.5.v20151012) > 129|Active | 1|Jetty :: Servlet Handling (9.3.5.v20151012) > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@felix.apache.org > For additional commands, e-mail: users-h...@felix.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@felix.apache.org For additional commands, e-mail: users-h...@felix.apache.org
