[
https://issues.apache.org/jira/browse/CAMEL-16564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Piotr Klimczak updated CAMEL-16564:
-----------------------------------
Description:
Camel Blueprint namespace handler is missing Spring Namespace declaration:
{code:java}
<blueprint xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0";>
<service interface="org.apache.aries.blueprint.NamespaceHandler">
<service-properties>
<entry key="osgi.service.blueprint.namespace">
<array value-type="java.lang.String">
<value>http://camel.apache.org/schema/spring</value> <!--
THIS IS MISSING -->
<value>http://camel.apache.org/schema/blueprint</value>
<value>http://camel.apache.org/schema/placeholder</value>
</array>
</entry>
</service-properties>
<bean class="org.apache.camel.blueprint.handler.CamelNamespaceHandler"/>
</service>
</blueprint> {code}
There is support implemented in Camel Blueprint project (partially), there is
even some test spring context, but no real test coverage for this.
Is it because Apache Camel community is abandoning such approach?
We have quite few integrations which we have to be able to run in both: Tomcat
and Karaf.
I can provide some patches and improvements, provided that the community is
interested in supporting such path, rather then me spending time and nobody
even accepting PRs.
was:
Camel Blueprint namespace handler is missing Spring Namespace declaration:
{code:java}
<blueprint xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0";>
<service interface="org.apache.aries.blueprint.NamespaceHandler">
<service-properties>
<entry key="osgi.service.blueprint.namespace">
<array value-type="java.lang.String">
<value>http://camel.apache.org/schema/spring</value> <!--
THIS IS MISSING -->
<value>http://camel.apache.org/schema/blueprint</value>
<value>http://camel.apache.org/schema/placeholder</value>
</array>
</entry>
</service-properties>
<bean class="org.apache.camel.blueprint.handler.CamelNamespaceHandler"/>
</service>
</blueprint> {code}
There is Support support implemented in Camel Blueprint project, there is even
some test spring context, but no real test coverage for this.
Is it because Apache Camel community is abandoning such approach?
We have quite few integrations which we have to be able to run in both: Tomcat
and Karaf.
I can provide some patches and improvements, provided that the community is
interested in supporting such path, rather then me spending time and nobody
even accepting PRs.
> Camel Blueprint Spring namespace handler not enabled
> ----------------------------------------------------
>
> Key: CAMEL-16564
> URL: https://issues.apache.org/jira/browse/CAMEL-16564
> Project: Camel
> Issue Type: Improvement
> Components: karaf, osgi
> Affects Versions: 3.9.0
> Reporter: Piotr Klimczak
> Priority: Major
>
> Camel Blueprint namespace handler is missing Spring Namespace declaration:
> {code:java}
> <blueprint xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0";>
> <service interface="org.apache.aries.blueprint.NamespaceHandler">
> <service-properties>
> <entry key="osgi.service.blueprint.namespace">
> <array value-type="java.lang.String">
> <value>http://camel.apache.org/schema/spring</value> <!--
> THIS IS MISSING -->
> <value>http://camel.apache.org/schema/blueprint</value>
> <value>http://camel.apache.org/schema/placeholder</value>
> </array>
> </entry>
> </service-properties>
> <bean
> class="org.apache.camel.blueprint.handler.CamelNamespaceHandler"/>
> </service>
> </blueprint> {code}
> There is support implemented in Camel Blueprint project (partially), there is
> even some test spring context, but no real test coverage for this.
> Is it because Apache Camel community is abandoning such approach?
> We have quite few integrations which we have to be able to run in both:
> Tomcat and Karaf.
> I can provide some patches and improvements, provided that the community is
> interested in supporting such path, rather then me spending time and nobody
> even accepting PRs.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
