Hi again David, Thanks again for this post! As you gave me the clue needed to temporarily get out of a very deep hole with Jetty connector discovery in one of our OSGi builds. Once I set Engine.setUserClassLoader(this.getClass().getClassLoader()); in my Equinox application, I can add the Jetty connector to the dependencies for the application bundle, and place a META-INF/services/org.restlet.engine.ServerHelper file in the source tree of my application bundle to point to Jetty (or programmatically set the Engine, but for my case it's a better temporary fix to externalize it in the file). It doesn't make the connector especially pluggable in an OSGi way, but it gets me out of dodge for today.
I have some ideas for improving this without breaking the core Restlet model, but will wait for Jerome to weigh in! - Rob On Mon, Feb 23, 2009 at 5:40 PM, David Fogel <[email protected]> wrote: > 3) How can we get the restlet engine to use, for example, the Jetty > connector, in the OSGI environment? We added the Jetty extension > bundle, as well as the various Jetty bundles, to our environment. But > I can't see any evidence that they're being used. the existing docs > only mention the conventional java jar-scanning technique, which > allows this to happen automatically in non-OSGi environments. > ------------------------------------------------------ http://restlet.tigris.org/ds/viewMessage.do?dsForumId=4447&dsMessageId=1239287
