[
https://issues.apache.org/activemq/browse/CAMEL-2697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Willem Jiang resolved CAMEL-2697.
---------------------------------
Fix Version/s: 2.3.0
(was: 2.4.0)
Resolution: Fixed
As we can't reproduce the issue with the test case, now I close this issue.
We can reopen it when we hit this kind of issue again.
> camel-spring - Spring 3.0.x - Add depends-on in the namespace handler to make
> it easy for end users to use Spring and Camel without considering ordering of
> their beans
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-2697
> URL: https://issues.apache.org/activemq/browse/CAMEL-2697
> Project: Apache Camel
> Issue Type: Improvement
> Components: camel-spring
> Affects Versions: 2.2.0, 2.3.0
> Reporter: Claus Ibsen
> Assignee: Willem Jiang
> Fix For: 2.3.0
>
>
> Spring 3.0.x behaves differently when discovering bean dependencies. For
> example if you have a <routeBuilder ref="xxx"/> in <camelContext/> than the
> {{xxx}} bean will not by default be dependent on the <camelContext/>. This
> causes Spring maybe to create the {{xxx}} before the {{camelContext}}. And
> you most likely want CamelContext to be created beforehand, so IoC allows you
> to inject CamelContext into that {{xxx}} or whatnot.
> See nabble
> http://old.nabble.com/Spring-3.0-and-Camel-2.2---Route-configure%28%29-called-before-Spring-beans-injected-ts28415437.html
> We do already have logic for this in the namespace handler, but we need to
> add it to more places to have it working for all kind of camel types.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
