Ok, I tested out the change and it works like a charm in unit test, but in
main class itself I think there is still some issue.
Lets take as an example Boot1.java from my example project, if I do this:
@Configuration
@EnableAutoConfiguration
@Import({*CamelAutoConfiguration.class,* CamelConfiguration.class})
public class Boot1 {
@Value("${name}")
String name;
public static void main(String[] args) {
SpringApplication.run(Boot1.class, args);
}
@Bean(name = "someProperty")
public String getPropertyValue() {
return name;
}
}
It works well, but if I remove CamelAutoConfiguration.class from imports,
then the issue is still the same (I guess CamelAutoConfiguration is
processed *after* my routes config).
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-boot-autowiring-issue-tp5758543p5758667.html
Sent from the Camel - Users mailing list archive at Nabble.com.
