I'm in a bit of a pickle with regards to using a scripting language with OSGi. Nothing insurmountable, but it is time consuming and I want to do it right.
I'm using the ScriptEngineManager API (JSR-223) to discover ScriptEngines. It does this via the JAR file service provider style: http://java.sun.com/javase/6/docs/technotes/guides/jar/jar.html#Service%20Provider ... In this case, it loads all resources named META-INF/services/javax.script.ScriptEngineFactory Consider the following set of bundles: javafx -- ScriptEngine implementation, has the ScriptEngineFactory file and some scripts gui -- the main UI bundle, whose scripts reference scripts in widgets. widgets -- some supplimental scripts So, several bits of classloader magic here: 1) Finding the ScriptEngineFactory file 2) Finding the implementation the above points to 3) finding my scripts 4) finding the scripts in widgets and javafx. What is the best mix of exports, imports and (the new-to-me) DynamicImport-Package) in this case? I seem to be finding myself setting up classloaders and all sorts of things just to get parts of the above working. However, I tend to die on step 1 even though I can manually ask the classloader to find the file for me. Do I need to list resources like scripts or the ScriptEngineFactory present as exported packages? Thanks, Pat. -- Defy mediocrity. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
