번들이 GracePeriod 상태로 유지됨

Question

내 낙타 경로에서 "cxf : cxfEndpoint"를 인스턴스화하려고합니다. 그러나 번들은 다음 로그에 "유예 기간"상태 유지 :

2016-11-10 11:03:07,598 | INFO | rint Extender: 1 | BlueprintContainerImpl   | ? ? | 21 - org.apache.aries.blueprint.core - 1.4.2 | Bundle com.entreprise.example is waiting for namespace handlers [http://camel.apache.org/schema/blueprint] 

그리고 내 camelContext.xml 파일은 다음과 같습니다 당신이 정말로 당신의 청사진 스키마를 엉망처럼

<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.0.0" 
xmlns:jaxws="http://cxf.apache.org/blueprint/jaxws" xmlns:cxf="http://cxf.apache.org/blueprint/core" 
xmlns:camel="http://camel.apache.org/schema/blueprint" xmlns:camelcxf="http://camel.apache.org/schema/blueprint/cxf" 
xsi:schemaLocation=" http://www.osgi.org/xmlns/blueprint/v1.0.0 http://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd 
http://cxf.apache.org/blueprint/jaxws http://cxf.apache.org/schemas/blueprint/jaxws.xsd 
http://cxf.apache.org/blueprint/core http://cxf.apache.org/schemas/blueprint/core.xsd"> 

<camelcxf:cxfEndpoint id="fist" 
    serviceClass="com.entreprise.example.services.firstService" 
    address="http://localhost:8181/cxf/example/firstMsg"> 
    <camelcxf:properties> 
     <entry key="dataFormat" value="POJO" /> 
     <entry key="loggingFeatureEnabled" value="true" /> 
    </camelcxf:properties> 
</camelcxf:cxfEndpoint> 
<camelcxf:cxfEndpoint id="second" 
    serviceClass="com.entreprise.example.services.secondService" 
    address="http://localhost:8181/cxf/example/secondMessage"> 
    <camelcxf:properties> 
     <entry key="dataFormat" value="POJO" /> 
     <entry key="loggingFeatureEnabled" value="true" /> 
    </camelcxf:properties> 
</camelcxf:cxfEndpoint> 
<camelContext trace="false" id="example" 
    xmlns="http://camel.apache.org/schema/blueprint"> 
    <route> 
     <from uri="cxf:bean:first" /> 
     <to uri="cxf:bean:second" /> 
    </route> 
</camelContext> 

Answer 1

이 보인다 선언. 아래

<?xml version="1.0" encoding="UTF-8"?> 
<blueprint xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0" 
    xmlns:cxf="http://camel.apache.org/schema/blueprint/cxf" 
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
    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"> 

처럼 뭔가 청사진 선언을 교체 그리고 당신은 어떤을 자유롭게 사용할 수 있지만 ("CXF"대신 더 명확하고 redeable가 될 엔드 포인트와 콩에 대한 접두사로 "camelcxf"의 사용 접두사를 사용하는 것을 선호합니다).

좋아, 다음과 같이 혼란 사용을 방지하기 위해이 해결할 수 종속성 오류를 기다리는 : 자주 앱이에 따라 일부 karaf 기능을 설치해야합니다 나타냅니다

<?xml version="1.0" encoding="UTF-8"?> 
<blueprint xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0" 
    xmlns:cm="http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.2.0" 
    xmlns:cxf="http://camel.apache.org/schema/blueprint/cxf" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
    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"> 

    <cxf:cxfEndpoint id="fist" 
     serviceClass="com.entreprise.example.services.firstService" address="http://localhost:8181/cxf/example/firstMsg"> 
     <cxf:properties> 
      <entry key="dataFormat" value="POJO" /> 
      <entry key="loggingFeatureEnabled" value="true" /> 
     </cxf:properties> 
    </cxf:cxfEndpoint> 
    <cxf:cxfEndpoint id="second" 
     serviceClass="com.entreprise.example.services.secondService" address="http://localhost:8181/cxf/example/secondMessage"> 
     <cxf:properties> 
      <entry key="dataFormat" value="POJO" /> 
      <entry key="loggingFeatureEnabled" value="true" /> 
     </cxf:properties> 
    </cxf:cxfEndpoint> 
    <camelContext trace="false" id="example" 
     xmlns="http://camel.apache.org/schema/blueprint"> 
     <route> 
      <from uri="cxf:bean:first" /> 
      <to uri="cxf:bean:second" /> 
     </route> 

</blueprint>