Re: blueprint:cm multiple bundle but same config file

David, (for some reason Google was filtering your email address from yahoo as a phishing attack) I agree and think that DS and the SCR are great for exposing and importing services. In Blueprint I'd use the normal service/reference mechanics in XML for that but can easily jettison it. But most

Re: blueprint:cm multiple bundle but same config file

This sounds like a good place to use the whiteboard pattern and marker properties. Using annotations requires a number of extra steps from the Camel/OSGi runtime, where a service property would just require a simple filter on the service registry lookup. Regards, Tim On 2 Aug 2016, at 02:44,

Re: blueprint:cm multiple bundle but same config file

Can you include scanning services or certain types of annotated services to inject camel things into? That way you can use DS components more easily. On 1 August 2016 at 20:03, Brad Johnson wrote: > The CamelContext disambiguation obviously is a next step... > > On

Re: blueprint:cm multiple bundle but same config file

The CamelContext disambiguation obviously is a next step... On Mon, Aug 1, 2016 at 8:01 PM, Brad Johnson wrote: > I'd thought that it was possible since the examples have a SimpleRegistry > and mention using it to register beans. But when I looked at the >

Re: blueprint:cm multiple bundle but same config file

I'd thought that it was possible since the examples have a SimpleRegistry and mention using it to register beans. But when I looked at the AbstractCamelRunner it became obvious that that would not work. I'm trying something by creating a new SCRRegistry type just for the sake of

Re: blueprint:cm multiple bundle but same config file

Tim, After working with DS and SCR a little I can understand its benefits. One obvious advantage was being able to write basic JUnit tests to test my routes without having to fire up CBTS. I've always disliked working in XML so it is odd being in the position like I sound like I'm the one

Re: blueprint:cm multiple bundle but same config file

me help and directions from experts. > > > -Kamesh > > > -- > From: timothyjw...@apache.org > To: user@aries.apache.org > Subject: Re: blueprint:cm multiple bundle but same config file > Date: Wed, 13 Jul 2016 08:34:41 + > > > H

RE: blueprint:cm multiple bundle but same config file

: blueprint:cm multiple bundle but same config file Date: Wed, 13 Jul 2016 08:34:41 + Hi Brad, I’ve been watching this thread for a while, and you’ve finally managed to draw me in :) On 12 Jul 2016, at 17:42, Brad Johnson <brad.john...@mediadriver.com> wrote: Gui

Re: blueprint:cm multiple bundle but same config file

apache.org] > *Envoyé :* mardi 12 juillet 2016 17:58 > *À :* user@aries.apache.org > *Objet :* Re: blueprint:cm multiple bundle but same config file > > > > I can happily review a patch if you're fancy writing one... > > > > And I disagree with the 'blueprint is d

RE: blueprint:cm multiple bundle but same config file

Objet : Re: blueprint:cm multiple bundle but same config file I can happily review a patch if you're fancy writing one... And I disagree with the 'blueprint is dead and nobody cares about it anymore'. What's dead is the blueprint osgi specification for blueprint, not the Aries Blueprint

Re: blueprint:cm multiple bundle but same config file

Hi Brad, I’ve been watching this thread for a while, and you’ve finally managed to draw me in :) On 12 Jul 2016, at 17:42, Brad Johnson > wrote: Guillaume, I'm still using Blueprint and have found Camel/SCR to be a pain to

Re: blueprint:cm multiple bundle but same config file

Guillaume, I'm still using Blueprint and have found Camel/SCR to be a pain to work with. It provides no tangible benefit if one is using Blueprint for routes and dependency injection anyway as it simply introduces one more way of configuring things. It was interesting to read the other day that

Re: blueprint:cm multiple bundle but same config file

I can happily review a patch if you're fancy writing one... And I disagree with the 'blueprint is dead and nobody cares about it anymore'. What's dead is the blueprint osgi specification for blueprint, not the Aries Blueprint project. I've recently added a bunch of important features related

Re: blueprint:cm multiple bundle but same config file

David, I'm all for multilocation support in blueprint. Can't wait for it. But it sounds like your saying blueprint is dead and nobody cares about it anymore so it doesn't seem likely to happen anytime soon. It certainly wouldn't be relevant to Fuse which uses R4 in any case. On Tue, Jul 12,

Re: blueprint:cm multiple bundle but same config file

I’d like to make sure I understand what you are doing here…. IIUC during the build of your project you are generating multiple configuration files with the same or similar content, and each of these is loaded into a configuration which is bound to a particular bundle location? So, at build

Re: blueprint:cm multiple bundle but same config file

Pablo, One possible solution to this problem that I'm currently looking at is using a configuration bundle along with my features bundle. In the configuration bundle I have all the cfg files and use properties placeholders ${value} to set the value for key/value. In the POM I load properties

Re: blueprint:cm multiple bundle but same config file

David, That is some pretty extreme and wild speculation alright. How does one use blueprint to not use OSGi appropriately? In the 5 years I've been consulting with Fuse/Karaf/OSGi and going to various clients not one of them used or uses DS. Not one. They all use bundles, services, and Camel

Re: blueprint:cm multiple bundle but same config file

I don’t think karaf is at osgi R4.2 any more, I suggest you look at the osgi R5 or R6 config admin spec for “multi location”. You guys might be using blueprint every day, but there is no OSGI spec work to keep it up to date or even specify obviously necessary features such as config admin

Re: blueprint:cm multiple bundle but same config file

It is in here; https://osgi.org/javadoc/r4v42/org/osgi/service/cm/ConfigurationAdmin.html A bundle is in aries bound to the pid. So it is actually working as expected, bit of a hassle since spring-dm allowed it. And

Re: blueprint:cm multiple bundle but same config file

Wow... that answer surprises me. My business works exclusively with Karaf, ServiceMix, ActiveMQ, CXF, and Camel. A large portion of it is heavily OSGi based. In all of my years, I still have yet to run into a single DS implementation, and I actually only heard of one that was used and was

Re: blueprint:cm multiple bundle but same config file

IMNSHO blueprint is only really plausible if you have a large amount of Spring based code and you need to convert it to be sort of osgi-compatible really quickly without understanding osgi or the code. Otherwise taking the time to understand DS and use it is much more satisfactory. DS

Re: blueprint:cm multiple bundle but same config file

My point is that should you wish to investigate this the place to start is finding the code that takes the .cfg file and uses it to create or modify a configuration in config admin, and find out whether it can set the bundle location to “?”. After you get that working then you can see if the

Re: blueprint:cm multiple bundle but same config file

If I were to sit down with the blueprint folks today to create a wish list one thing I'd like to see is for an ability to have a configuration hierarchy specified with parent/child relationships much like one has in Maven. Have a base configuration file and be able to have another cfg file

Re: blueprint:cm multiple bundle but same config file

Ray, If I understand your question right the answer is the Aries extension is referencing configuration. In karaf/fuse for example the following: will load properties from etc/com.my.foo.cfg Installing that file is done either manually or by use of a features file. Whenever I've attempted

Re: blueprint:cm multiple bundle but same config file

Ok, so after a brief review the cm schema is an Aries extension and it doesn't appear to support the location binding. However, it's unclear to me whether this extension is creating the configuration or merely referencing one from outside. Any Aries gurus can answer that? - Ray On Thu, Jul 7,

Re: blueprint:cm multiple bundle but same config file

I’m not really familiar with blueprint cm but I’d expect that to indicate which pid to use to fetch the config from config admin and in the ... how to map configuration propertiething blueprint substitution knows about. Is that really instructions to create a new configuration and populate it

Re: blueprint:cm multiple bundle but same config file

I’d say the first question is whether common management agents (felix fileinstall???) let you specify the bundle location. The second is whether blueprint cm accepts the “?” multi-location. david jencks > On Jul 7, 2016, at 8:18 AM, Raymond Auge wrote: > > So I

Re: blueprint:cm multiple bundle but same config file

Aye, there's the rub. And obviously many of us aren't on the bleeding edge of blueprint or OSGi either so some of these features may be new and in place now. I've had to use work arounds for this in the past like creating my own OSGi service to share configuration data. On Thu, Jul 7, 2016 at

Re: blueprint:cm multiple bundle but same config file

David, I agree with everything you've said, however this looks like blueprint being the agent here: ... - Ray On Thu, Jul 7, 2016 at 11:18 AM, David Jencks wrote: > No, blueprint cm shouldn’t really know about the multi-location. The > management agent that

Re: blueprint:cm multiple bundle but same config file

So I guess the question comes down to how configurable is blueprint in this regard! that's the part I don't know. - Ray On Thu, Jul 7, 2016 at 11:17 AM, David Jencks wrote: > Neither one, the bundleLocation on the configuration is set. This is > something config admin

Re: blueprint:cm multiple bundle but same config file

No, blueprint cm shouldn’t really know about the multi-location. The management agent that is creating the configuration should be setting the bundle location to the multi-location ”?”. david jencks > On Jul 7, 2016, at 8:12 AM, Pablo Gómez Pérez wrote: > > I see and

Re: blueprint:cm multiple bundle but same config file

Ray, When you say bound to the bundle do you mean that it physically resides in the jar/bundle or do you mean bound via the blueprint properties persistent-id? Brad On Thu, Jul 7, 2016 at 9:41 AM, Raymond Auge wrote: > As long as configurations are not bound to a

Re: blueprint:cm multiple bundle but same config file

As long as configurations are not bound to a bundle they can be used by any bundle. The exception clearly shows that the configuration is bound to a bundle. Creating an unbound configuration requires passing a "?" as the second arguments to getConfiguration/createFactoryConfiguration methods of

blueprint:cm multiple bundle but same config file

Hello All, Is it possible to use same config file from multiple bundles while using Config Admin with blueprint Blueprint? Because, I can't manage to do that, I get the following error: MESSAGE Cannot use configuration test.mybundle for [org.osgi.service.cm.ManagedService, id=214,