[
https://issues.apache.org/activemq/browse/CAMEL-1873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=53448#action_53448
]
Claus Ibsen commented on CAMEL-1873:
------------------------------------
I think its a bit of a *hack* to use reflection to invoke a getter for
CamelContext to test whether it has already been set.
I would prefer in Camel 2.0 to add a {{getCamelContext}} method to the
CamelContextAware interface to avoid the reflection hack.
And the best would be that we had a bit better control on the bean post
processor and which camel context it belongs to.
> template , consumerTemplate, service, proxy can't be set with right camel
> context if there are more than one camel context in the spring application
> context
> ------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-1873
> URL: https://issues.apache.org/activemq/browse/CAMEL-1873
> Project: Apache Camel
> Issue Type: Bug
> Components: camel-spring
> Affects Versions: 1.4.0, 1.5.0, 1.6.0, 2.0-M1, 1.6.1, 2.0-M2, 2.0-M3
> Reporter: Willem Jiang
> Assignee: Willem Jiang
> Fix For: 1.6.2, 2.0.0
>
>
> Current camel support to define a producer template OUTSIDE a camel context,
> I think it works well just like the autowire function which is provided in
> Spring.
> If there more than two Camel context in the Spring Application context , the
> user should specify the camel context which the template should use.
> But I have a concern that even we put the template INSIDE the camel context,
> the template will not be set with a right version of camel context, since we
> use a CamelPostProcessor to inject CamelContext.
> So I did a quick test on the current Camel code and found there is a bug if
> there are more one CamelContext -- CamelPostProcessor will inject the last
> create camel context into the CamelContextAware object.
> Since it is not easy to add the camelContext referece id into the template
> element attribute, we'd better just support to parser these elements inside
> the camel context.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
