Return-Path: X-Original-To: apmail-camel-issues-archive@minotaur.apache.org Delivered-To: apmail-camel-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id DE24C10FEC for ; Wed, 25 Feb 2015 08:50:04 +0000 (UTC) Received: (qmail 23242 invoked by uid 500); 25 Feb 2015 08:50:04 -0000 Delivered-To: apmail-camel-issues-archive@camel.apache.org Received: (qmail 23201 invoked by uid 500); 25 Feb 2015 08:50:04 -0000 Mailing-List: contact issues-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@camel.apache.org Delivered-To: mailing list issues@camel.apache.org Received: (qmail 23191 invoked by uid 99); 25 Feb 2015 08:50:04 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 Feb 2015 08:50:04 +0000 Date: Wed, 25 Feb 2015 08:50:04 +0000 (UTC) From: "Rasmus Larsen (JIRA)" To: issues@camel.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Comment Edited] (CAMEL-7122) javascript language not resolving MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CAMEL-7122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14334819#comment-14334819 ] Rasmus Larsen edited comment on CAMEL-7122 at 2/25/15 8:49 AM: --------------------------------------------------------------- I'm experiencing the same issue on Camel 2.14.1. I have not tested it on any other versions of camel. The work-around from http://stackoverflow.com/a/21018603 solves the issue on Camel 2.14.1 EDIT: I spoke to quickly. After a re-install of the Karaf, the work-around no longer works. I'm not sure why but last time a tried a bunch of different deploys, so some of the deploys may not have been properly undeployed. EDIT #2: The work-around works when both camel-script and camel-script-javascript features are installed on Karaf. The work-around does not work when either of those dependencies (or both) are not installed as features on Karaf but instead are embedded in the bundle jar file containing the camel context. was (Author: rlarsen5): I'm experiencing the same issue on Camel 2.14.1. I have not tested it on any other versions of camel. The work-around from http://stackoverflow.com/a/21018603 solves the issue on Camel 2.14.1 EDIT: I spoke to quickly. After a re-install of the Karaf, the work-around no longer works. I'm not sure why but last time a tried a bunch of different deploys, so some of the deploys may not have been properly undeployed. > javascript language not resolving > --------------------------------- > > Key: CAMEL-7122 > URL: https://issues.apache.org/jira/browse/CAMEL-7122 > Project: Camel > Issue Type: Improvement > Components: camel-script, osgi > Affects Versions: 2.10.0 > Environment: JBoss Fuse 6.0.0, windows > Reporter: Steve Murphy > Assignee: Claus Ibsen > Priority: Minor > Labels: javascript > Fix For: 2.12.3, 2.13.0 > > > .when().javascript("3 > 1 + 1") causes bundle not to be loaded, with the following error: > ERROR | BluePrinntContainerImpl | Bundle my-service is waiting for dependencies > [(&(language=js)(objectClass=org.apache.camel.spi.LanguageResolver))] > It seems that the javascript language is not registered correctly. > Adding a custom Activator to register languages found by all ScriptEngineFactory's, and registering Rhino engine as "js" instead of "ECMAScript" seems to solve the problem. > This problem is in 2.10.0. I have no idea if it has been fixed in other versions. > Can someone please check .javascript() functionality in 2.11? Since if it has indeed been fixed in future versions, then this bug can be closed :) > Workaround posted here: > http://stackoverflow.com/questions/20997276/jboss-fuse-apache-camel-wont-resolve-language-js-javascript-for-bundle -- This message was sent by Atlassian JIRA (v6.3.4#6332)