[
https://issues.apache.org/jira/browse/CAMEL-16564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17337170#comment-17337170
]
Piotr Klimczak edited comment on CAMEL-16564 at 4/30/21, 8:25 AM:
------------------------------------------------------------------
[~davsclaus] thanks for your explanation.
I think there is some misunderstanding however.
I am not asking for camel-blueprint to support Spring XMLs. This is what Aries
Blueprint Spring does.
I am only asking for handling [http://camel.apache.org/schema/spring]
namespace by Camel Karaf (blueprint component).
You are surely aware there is Aries Blueprint Spring project which embeds
Spring within Blueprint- so Blueprint can read Spring XML and they can work
together in single application context.
This works actually quite well with some limitations and is very helpful where
there is requirement for XML DSL to work in Karaf and Tomcat container.
However in such scenario and without above fix, a bundle with Spring XML (which
has Camel Spring XML) hangs in grace period due to not finding namespace
handler for [http://camel.apache.org/schema/spring.]
So from that perspective it is missing, as adding this line registers namespace
handler in OSGi correctly and Spring Camel route starts correctly, except it
starts as Blueprint context and not Spring context- which is not a problem.
The only remaining problem I have is making Camel to correctly recognise
properties, which might be either Camel Karaf or Aries Blueprint Spring fix.
But anyway, I am slightly confused what next in light of above answers.
was (Author: nannou9):
[~davsclaus] thanks for your explanation.
I think there is some misunderstanding however.
I am not asking for camel-blueprint to support Spring XMLs. This is what Aries
Blueprint Spring does.
I am only asking for handling [http://camel.apache.org/schema/spring] namespace
by Camel Karaf (blueprint component).
You are surely aware there is Aries Blueprint Spring project which embeds
Spring within Blueprint- so Blueprint can read Spring XML and they can work
together in single application context.
This works actually quite well with some limitations and is very helpful where
there is requirement for XML DSL to work in Karaf and Tomcat container.
However in such scenario and without above fix, a bundle with Spring XML (which
has Camel Spring XML) hangs in grace period due to not finding namespace
handler for [http://camel.apache.org/schema/spring.]
So from that perspective it is missing, as adding this line registers namespace
handler in OSGi correctly and Spring Camel route starts correctly, except it
starts as Blueprint context and not Spring context- which is not a problem.
The only remaining problem I have is making Camel to correctly recognise
properties, which might be either Camel Karaf or Aries Blueprint Spring fix.
But anyway, I am slightly confused what next.
> 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)
