Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
1.4.0, 1.5.0, 1.6.0, 2.0-M1, 1.6.1, 2.0-M2, 2.0-M3
-
None
Description
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.