I guess the current bundles are accessible to the DefaultSlingScript
resolver (assuming they are active and an entry for META-INF/services/
javax.script.ScriptEngineFactory), I was thinking that it might be
nice to have their packages exported rather than remain private. I
guess, though, then people might start using them without going
through the script resolver...
-paddy
On Jan 8, 2008, at 12:02 PM, Padraic Hannon wrote:
I'd like to update the various ScriptEngineFactories so that they
provide their services via osgi. This way the registration of
factories can be done via standard osgi bundle activation. This
would allow the default script resolver to access Freemarker and the
other engines, and could be used for microSling as well.
WDYT?
paddy
