[
https://issues.apache.org/jira/browse/CAMEL-3481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen updated CAMEL-3481:
-------------------------------
Fix Version/s: (was: 2.6.0)
3.0.0
Camel 3.0 will be JDK 1.6+ only so we target this for Camel 3
> camel-script doesn't work in OSGi
> ---------------------------------
>
> Key: CAMEL-3481
> URL: https://issues.apache.org/jira/browse/CAMEL-3481
> Project: Camel
> Issue Type: Improvement
> Components: camel-script
> Affects Versions: 2.5.0
> Reporter: Aaron Mulder
> Assignee: Aaron Mulder
> Priority: Minor
> Fix For: 3.0.0
>
> Attachments: camel-core.patch, camel-script.patch
>
>
> In an OSGi environment, the ScriptEngineManager that ScriptBuilder uses can't
> find any scripting engines except the ones packaged in the JDK (Rhino, maybe
> AppleScript, etc.). It's possible that setting a better ClassLoader would
> work, or perhaps using a singleton ScriptEngineManager and setting up the
> scripting engines in an OSGi Activator instead of relying on the META-INF
> lookup every time a script is invoked.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
