I've tried to find ways to override the values of a pid, though haven't dug
into it in depth.  Also the possibility of using multiple pids in a single
blueprint (achieving much the same.)

Theoretically it is possible and I think it is in DS but I'm not a big user
of DS so don't take that as gospel.  I think even blueprint permits but the
problem is in the implementation (again don't quote me on that one.) My
recollection is that it should be possible but the Camel blueprint and
Aries of at least some earlier versions didn't support it.  I've become so
used to using a single PID that I don't worry about it. One solution is you
can create an OSGi service for the functionality that is required by and
shared between the bundles and call that service instead of duplicating it
across bundles.

Brad

On Fri, Sep 16, 2016 at 4:20 AM, owain <owain@integration.technology> wrote:

> Ranx,
>
> Thanks for the tip.  I have a parent project (POM) and modules, one each
> for
> services.  So currently I have a pid for each service but some of the cfg
> settings are common across projects (e.g. kafka server address which is a
> pointer to a docker linked container).
>
> What would be cool would be to have some defaults in a parent pid and then
> over-rides and additional ones in the modules pid (or same pid?).  Is there
> a way to do this?
>
> Additionally, some of the properties should not be in git since they are
> "secure".  At the moment I am deploying them via a volume mount from the
> fuse docker container to /etc and intend to manage them via a fabric
> profile
> (next stage).  Any tips on this.
>
> A very useful reply, might be a blog post?  Only the basics are covered in
> the Camel in Action and Cookbook.
>
> Thanks again.
>
> O.
>
>
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.
> com/Fuse-Blueprint-properties-override-tp5787541p5787633.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>

Reply via email to