camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bart Horré (JIRA) <>
Subject [jira] [Created] (CAMEL-8546) No LanguageResolver found for language=js
Date Wed, 25 Mar 2015 16:07:53 GMT
Bart Horré created CAMEL-8546:

             Summary: No LanguageResolver found for language=js
                 Key: CAMEL-8546
             Project: Camel
          Issue Type: Bug
            Reporter: Bart Horré

{noformat}Unable to start blueprint container for bundle test.xml due to unresolved dependencies
        at org.apache.aries.blueprint.container.BlueprintContainerImpl$[10:org.apache.aries.blueprint:0.3.2]
        at java.util.concurrent.Executors$[:1.7.0_17]
        at java.util.concurrent.FutureTask$Sync.innerRun([:1.7.0_17]
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201([:1.7.0_17]
        at java.util.concurrent.ScheduledThreadPoolExecutor$[:1.7.0_17]
        at java.util.concurrent.ThreadPoolExecutor.runWorker([:1.7.0_17]
        at java.util.concurrent.ThreadPoolExecutor$[:1.7.0_17]
        at[:1.7.0_17] {noformat}

This happens when we try to use script with blueprint because blueprint tries to resolve the
LanguageResolver with filter language=js. However camel.osgi registered a default LanguageResolver
under resolver=default which causes blueprint to wait for ever.

This message was sent by Atlassian JIRA

View raw message