Yes, you would create 1 feature for the jars to provide the functionality and then a feature per-configuration. The ‘configuration features’ would only contain cfg files (instead of jars) to activate the services with different configurations.
-Matt > On Nov 30, 2022, at 6:15 AM, 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.
