Details
-
Enhancement
-
Resolution: Unresolved
-
Major
-
None
-
10.0.0.AM2
-
None
Description
Support for Spring Beans includes the ability to import a separate file with a set of beans. If the config that imports beans from elsewhere tries to reference one of the beans in another file, right now we do not support that kind of approach.
The example I can find that imports a beans.xml file that actually defines more beans is here: https://github.com/apache/camel/tree/master/examples/camel-example-cafe
But it does not define a bean in the Camel configuration that relies on a bean in the imported file. If you were to create a factory-style bean that was defined in src/main/resources/meta-inf/beans.xml and then tried to reference it in the config via a bean reference, right now you are unable to define it in the tooling and if you define it in the source, it flags it as a validation error because it can't find a bean with the correct ID in the camel configuration.
We would need to find a way to process imports so that IDs would be validated across not only the configuration at hand, but the imported configuration files as well.