【问题标题】:Bundle is waiting for namespace handlers [http://camel.apache.org/schema/blueprint]Bundle 正在等待命名空间处理程序 [http://camel.apache.org/schema/blueprint]
【发布时间】:2016-04-19 14:46:50
【问题描述】:

我编写了一个简单的 apache camel 项目,最终将部署在 FUSE 容器中。现在,我只是想让一个基本的单元测试工作。我以示例 here 为起点。

我编写了可以工作的单元测试,但是当我包含一个蓝图文件时,我在测试输出中得到以下条目:

Bundle TestMainRoute is waiting for namespace handlers [http://camel.apache.org/schema/blueprint]

测试失败,堆栈跟踪如下:

java.lang.RuntimeException: Gave up waiting for service (objectClass=org.apache.camel.CamelContext)
at org.apache.camel.test.blueprint.CamelBlueprintHelper.getOsgiService(CamelBlueprintHelper.java:240)
at org.apache.camel.test.blueprint.CamelBlueprintHelper.getOsgiService(CamelBlueprintHelper.java:202)
at org.apache.camel.test.blueprint.CamelBlueprintTestSupport.createCamelContext(CamelBlueprintTestSupport.java:352)
at org.apache.camel.test.junit4.CamelTestSupport.doSetUp(CamelTestSupport.java:247)
at org.apache.camel.test.junit4.CamelTestSupport.setUp(CamelTestSupport.java:217)
at org.apache.camel.test.blueprint.CamelBlueprintTestSupport.setUp(CamelBlueprintTestSupport.java:183)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)
at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:24)
at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)
at org.junit.rules.RunRules.evaluate(RunRules.java:20)
at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:271)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:70)
at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:50)
at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)
at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)
at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)
at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)
at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)
at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)
at org.junit.runners.ParentRunner.run(ParentRunner.java:309)
at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50)
at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)
at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)

我的xml很简单:

<blueprint xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0">
  <routeContext id="validationRoute"  xmlns="http://camel.apache.org/schema/blueprint" >

    <route id="validation">
        <from uri="direct:validation" />
        <log message="validating..." />
    </route>
</routeContext>

代码如下:

public class RouteTest extends CamelBlueprintTestSupport  {

  @Test
  public void testValidationRoute() throws Exception    {
    DefaultExchange r1 = new DefaultExchange(context);
    r1.getIn().setBody("");
    Exchange response1 = template.send("direct:validation", r1);
  }

  protected String getBlueprintDescriptor() {
    return "OSGI-INF/blueprint/blueprint.xml";
  1. 列表项

} }

注意,我的主要骆驼上下文引用了验证路线:

public class IntegrationFramework extends RouteBuilder {

public void configure() {

    from("netty-http:http://localhost:8457/broker/router.jsp").convertBodyTo(String.class)
    .log("http router "+simple("${body}").getText())
    .to("direct:validation");
}

我有其他单元测试和日志表明这部分工作正常。

【问题讨论】:

  • 您确实安装了骆驼蓝图功能,不是吗?
  • 您的 Camel 和 JBoss Fuse 版本是什么?
  • 必须在 CamelContext 中引用 RouteBuilder,RouteBuilder 不是 CamelContext。你有 CamelContext 吗?
  • camel版本为2.15.1.redhat-620133,pom.xml包含camel-blueprint、camel-test和camel-test-blueprint。我不是在 fuse 上运行它,而是在 eclipse 中运行它。
  • 您需要安装 camel-netty-http 组件,因为您在其中一条路线中使用它:feature-install camel-netty-http

标签: java apache-camel jbossfuse blueprint-osgi


【解决方案1】:

我遇到了同样的错误,但在 @mdarwin 之后进行了另一个设置,所以我也想与您分享我的解决方案。

我用camel-archetype-blueprint 开始了一个项目,所以我的命名空间如下所示:

blueprint xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0"
   xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
   xmlns:cm="http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.1.0"
   xsi:schemaLocation="
     http://www.osgi.org/xmlns/blueprint/v1.0.0 https://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd
     http://camel.apache.org/schema/blueprint http://camel.apache.org/schema/blueprint/camel-blueprint.xsd
     http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.1.0 http://aries.apache.org/schemas/blueprint-cm/blueprint-cm-1.1.0.xsd">

一开始它是一个非常简单的蓝图,带有一个计时器和一个文件端点,所以这里的实现并不重要。我将我的包部署到 Karaf 并为此安装了 aries-blueprint 功能。

我错过了,我真的很惭愧,也安装了camel。为此,我必须添加 repo 并安装它,您可以阅读 here:

feature:repo-add camel
feature:install camel

现在命名空间处理程序就在那里。

我认为这很明显,但还是花了几分钟才弄明白。

【讨论】:

    【解决方案2】:

    原来routeContext只存在于xml dsl的上下文中,无法从Java DSL中引用。我认为这是一个错误,因为它限制了混合 xml 和 java 配置的灵活性。

    通过将 routeContext 更改为 camelContext,这解决了问题。

    另请参阅此问题:Camel: importing routeContext into an external camelContext

    还相关:https://issues.apache.org/jira/browse/CAMEL-5717

    【讨论】:

    • 根据camel.apache.org/configuring-camel.htmlAlso notice that you can mix and match, having routes inside CamelContext and also externalized in RouteContext.
    • 感谢您的反对。我看不出链接中的内容与我在回答中所说的相矛盾。如果您可以在 java 中引用 routeContext,请告诉我如何让我的示例正常工作。
    猜你喜欢
    • 2020-01-29
    • 1970-01-01
    • 1970-01-01
    • 2013-03-23
    • 1970-01-01
    • 1970-01-01
    • 2018-09-23
    • 1970-01-01
    • 2019-09-02
    相关资源
    最近更新 更多