For me, the only issue so far is that Blueprint does not rewire after a config change. Seems to work other than that.
Best regards, Alex soto > On Feb 3, 2017, at 10:40 AM, Tim Ward <tim.w...@paremus.com> wrote: > > I disagree with the earlier statement that Blueprint and DS cannot coexist in > the same bundle. I have thought quite hard about this and can think of no > reason whatsoever why it should not work. > > Tim > > Sent from my iPhone > >> On 3 Feb 2017, at 15:28, Christian Schneider <ch...@die-schneider.net> wrote: >> >> I fully agree. I never understood why this decision was made for config >> admin. In newer versions of the spec it now is possible to share configs but >> in practice I had lots of problems with it. Still sometimes a common service >> can help. >> >> Christian >> >>> On 03.02.2017 16:13, Alex Soto wrote: >>> 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 >>> alex.s...@envieta.com >> >> -- >> Christian Schneider >> http://www.liquid-reality.de >> >> Open Source Architect >> http://www.talend.com >>
