You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Jean-Baptiste Onofré (Jira)" <ji...@apache.org> on 2022/05/02 15:07:00 UTC
[jira] [Assigned] (CAMEL-16564) camel-blueprint-spring - A new module to load Spring XML with Camel in OSGi
[ https://issues.apache.org/jira/browse/CAMEL-16564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Baptiste Onofré reassigned CAMEL-16564:
--------------------------------------------
Assignee: Jean-Baptiste Onofré
> camel-blueprint-spring - A new module to load Spring XML with Camel in OSGi
> ---------------------------------------------------------------------------
>
> Key: CAMEL-16564
> URL: https://issues.apache.org/jira/browse/CAMEL-16564
> Project: Camel
> Issue Type: New Feature
> Components: karaf, osgi
> Affects Versions: 3.9.0
> Reporter: Piotr Klimczak
> Assignee: Jean-Baptiste Onofré
> Priority: Major
> Fix For: 3.x
>
>
> 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.20.7#820007)