Hi, You can create a "core" feature installing the common bundles (so routes). This feature has a requirement to "my-configuration".
Then, you can have a different set of features providing the configurations, and also providing the "capability" my-configuration. At runtime, you have to install the "configuration" feature you want and the core feature can use it. It could be done at runtime or build time, depending of your needs. I hope it helps. Regards JB On Wed, Nov 30, 2022 at 1:15 PM Ephemeris Lappis <[email protected]> wrote: > > Hello. > > I'm almost sure that my question will seem stupid and perhaps leads to > ironic answers... > > I'd like to build a feature to define some "templated" services (JDBC > data sources for example, or custom services), that should be exactly > based on the same definition, but must be instantiated multiple times > with distinct configurations. The goal in our global ESB platform is > to provide generic Camel routes that will run for an undefined number > of business entities. Each entity could be deployed as a feature with > its own configuration. Some of the global services use the whiteboard > pattern to collect implementations for any number of businesses. > > The trivial way could be copying a full project to build as many > features as needed, but this is not a very good way to avoid > duplicated code and maintain them... > > Any ideas on how to do that ? > > Thanks a lot. > > Regards.
