title: Is OSGi fundamentally incompatible with JSR-223 Scripting Language Discovery?
body: <p>I've recently written a small specialist scripting language and used the Maven to export an OSGi compliant bundle that also exports a service descriptor into the "<code>META-INF/services/javax.script.ScriptEngineFactory</code>" service registry file.</p>
  
  <p>The problem is that although the OSGi import and export packages are fine, the service registry appears to be incompatible with OSGi (as OSGi keeps its bundles off the general classpath and uses separate classloaders for modules).</p>
  
  <p>My question is, am I correct in thinking that OSGi is incompatible with the Service Discovery mechanism, and if not, what can I add to my bundle metadata so that <code>ScriptEngineManager.getEngineFactories()</code> will list my script engine in an OSGi environment?</p>