[CAMEL-18862] Using Spring Boot Camel Starter the RoutesCollector doesn't see RoutesBuilder added via Camel Context Registry

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 3.20.2, 3.21.0
• Component/s: camel-spring-boot
• Estimated Complexity: Unknown

Language

Java

• Assignee: Claus Ibsen
• Reporter: Eduard Gomoliako
• Created: 04/Jan/23 16:22
• Updated: 10/Jan/23 11:12
• Resolved: 06/Jan/23 18:54

Description

Running Camel Context via Spring Boot Camel Starter the following configuration doesn't work:

@Configuration
public class ContextConfiguration {
  @Inject
  CamelContext camelContext;

  @PostConstruct
  public void init() {
    camelContext.getRegistry().bind("my-routes", new RoutesBuilder() {
      public void configure() {
        from("direct:input").to("direct:output");
      }
    });
  }
}

The reason seems to be in the SpringBootRoutesCollector class implementation that overrides the findByType method and makes it to use Spring ApplicationContext directly.

Considering that being bootstrapped via Spring Boot the Camel Context Registry looks the beans up in the Spring Application Context with a fallback to the default registry, the SpringBootRoutesCollector class is redundant and doesn't provide any additional value having only the mentioned findByType method overridden.

 

Should my analysis be incorrect, it would be nice to learn about the reasoning behind the SpringBootRoutesCollector class.

I appreciate your consideration.