You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2011/03/12 11:09:59 UTC

[jira] Assigned: (CAMEL-3481) camel-script doesn't work in OSGi

     [ https://issues.apache.org/jira/browse/CAMEL-3481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen reassigned CAMEL-3481:
----------------------------------

    Assignee: Willem Jiang  (was: Aaron Mulder)

> 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: Willem Jiang
>             Fix For: 2.8.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.
For more information on JIRA, see: http://www.atlassian.com/software/jira