[CAMEL-16564] camel-blueprint-spring - A new module to load Spring XML with Camel in OSGi

• Type: New Feature
• Status: Resolved
• Priority: Minor
• Resolution: Won't Fix
• Affects Version/s: 3.9.0
• Fix Version/s: 3.x
• Component/s: karaf, osgi
• Estimated Complexity: Unknown
• Assignee: Jean-Baptiste Onofré
• Reporter: Piotr Klimczak
• Created: 29/Apr/21 19:47
• Updated: 02/Sep/22 17:52
• Resolved: 02/Sep/22 17:52

Description

Camel Blueprint namespace handler is missing Spring Namespace declaration:

<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> 

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.

Issue Links

• is blocked by: ARIES-2045 Blueprint Spring not able to resolve bean by type
• is blocked by: ARIES-2046 Blueprint Spring to allow bundle blacklist to prevent unwanted namespace registration