No, services should be small and highly cohesive. Just because they need the same configuration setting, it does not mean they provide the same functionality or should be combined. This CM limitation is actually pushing for bigger less cohesive services. I am disappointed having invested in the CM for configuration, and it will cause me painful project delays now.
Best regards, Alex soto [email protected] > On Feb 3, 2017, at 10:04 AM, Christian Schneider <[email protected]> > wrote: > > In most cases sharing the same pid means you have some duplication in > functionality. So maybe you can have a service that is configured using this > pid and that provides functionality for both. > > Christian > > On 03.02.2017 16:01, Alex Soto wrote: >> Thanks, although I am curious why this would be. >> >> This puts me in quite a predicament, on the one side, two bundles >> referencing the same PID does not work, and on the other, DS and Blueprint >> can't coexisting in the same bundle. The only path I see is to not use the >> Configuration Manager at all, loosing the auto-reload, or to separate DS and >> Blueprint in two bundles, with two different configuration PIDs having the >> same settings, leading to redundant configurations. Not good either way. >> >> >> Best regards, >> Alex soto >> >> >>> On Feb 3, 2017, at 9:22 AM, Christian Schneider <[email protected]> >>> wrote: >>> >>> As long as it is not in the same bundles mixing DS and blueprint is fine. >>> >>> I guess that using the same config pid in two bundles or two frameworks is >>> the main problem. I had lots of problems when I tried this. >>> Theoretically sharing a config pid can work now as far as I know but I >>> would not bet on it. >>> >>> Christian >>> >>> On 03.02.2017 15:19, Alex Soto wrote: >>>> As far as I can tell, the problem occurs regardless of wether the DS >>>> component is (or not) in a separate bundle. >>>> My project is a mix of Camel routes defined in Blueprint DSL with some of >>>> the Camel routes calling services defined as DS components. >>>> Is this not a common/valid scenario? >>>> >>>> Best regards, >>>> Alex soto >>> -- >>> Christian Schneider >>> http://www.liquid-reality.de >>> >>> Open Source Architect >>> http://www.talend.com >>> > > > -- > Christian Schneider > http://www.liquid-reality.de > > Open Source Architect > http://www.talend.com >
