Scripting using JSR 223 in an OSGi environment

When providing scripting in a Java application, scripting engines conforming to JSR 223 (e.g. Groovy, JRuby, Scala, …) can easily be embedded using something along the lines of

ScriptEngineManager scriptEngineManager = new ScriptEngineManager();
ScriptEngine scriptEngine = scriptEngineManager.getByName("groovy");

However, in an OSGi-based application, the ScriptEngineManager fails to discover scripting engines located in installed bundles bundles, due to the way () it discovers engines available on the class path. Luckily, the Apache Felix project has already solved this problem, there are

which provide an OSGi-compliant way to discover and load scripting engines installed as OSGi bundles.

ScriptEngineManager scriptEngineManager = new OSGiScriptEngineManager(bundleContext);
ScriptEngine scriptEngine = scriptEngineManager.getByName("groovy");
About these ads
This entry was posted in Java, OSGi. Bookmark the permalink.

2 Responses to Scripting using JSR 223 in an OSGi environment

  1. Dave says:

    What bundle contains these classes? I see it is in the mishell folder, but don’t see that has a downloadable bundle.

    • Matt says:

      A quick search on Maven Central confirmed that these classes don’t seem to be in any bundle on there. I guess the best option would be to copy the mentioned three classes to your project, if your license is compatible with Apache v2 that shouldn’t be an issue.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s