camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Claus Ibsen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAMEL-3481) camel-script doesn't work in OSGi
Date Thu, 14 Apr 2011 14:21:05 GMT

    [ https://issues.apache.org/jira/browse/CAMEL-3481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13019843#comment-13019843
] 

Claus Ibsen commented on CAMEL-3481:
------------------------------------

Willem can you add the try .. finally in the code where you change the classloader on the
context. We must be sure we don't mess with that, in case an exception or something happens.


> 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

Mime
View raw message