Re: Services, start levels, and waiting

Thank you so much for this. I will join that list as well and try to do a better job keeping up with emails. David On 2015-09-07 20:31, Benson Margulies wrote: > I got it with a ton of help from other people on the felix list. The > CXF part is trivial. > > 1: Make a component with no ser

Re: Services, start levels, and waiting

I got it with a ton of help from other people on the felix list. The CXF part is trivial. 1: Make a component with no services: @Component(configurationPid = "com.basistech.ws.worker", configurationPolicy = ConfigurationPolicy.REQUIRE, /* No services; we're here to register ourself wi

Re: Services, start levels, and waiting

When you figure out how to add providers and services to cxf without blueprint please follow up. It would be helpful to me as well. Thanks for all your great questions, David On 2015-09-07 09:31, Benson Margulies wrote: > On Mon, Sep 7, 2015 at 9:28 AM, Benson Margulies wrote: > On Mon,

Re: Services, start levels, and waiting

On Mon, Sep 7, 2015 at 9:28 AM, Benson Margulies wrote: > On Mon, Sep 7, 2015 at 9:25 AM, Achim Nierbeck > wrote: >> hmm, must have overseen that sentence: >> >>> The onl difference in >>> bundle inventory from blueprint to DS is the addition of the >>> compendium jar, which is not even loaded

Re: Services, start levels, and waiting

On Mon, Sep 7, 2015 at 9:25 AM, Achim Nierbeck wrote: > hmm, must have overseen that sentence: > >> The onl difference in >> bundle inventory from blueprint to DS is the addition of the >> compendium jar, which is not even loaded by loading up CXF. > > > actually it's no good idea to include that

Re: Services, start levels, and waiting

hmm, must have overseen that sentence: The onl difference in > bundle inventory from blueprint to DS is the addition of the > compendium jar, which is not even loaded by loading up CXF. actually it's no good idea to include that, and afaik all of the felix bundles already provide all of the nee

Re: Services, start levels, and waiting

Achim and David, I am not currently using the most recent felix resolver; that requires building the trunk of Karaf with a patch. Over on the Karaf list, I'm pestering Achim with the following situation: I have, now, a working version of my system which is 100% blueprint. (I did solve the proble

Re: Services, start levels, and waiting

The felix-resolver does actually look for those Require-Capabilities and throws an error if they can't be met. Now karaf uses this resolver to resolve all features, and therefore will run into the same issue when installing a feature as installing a bundle. regards, Achim 2015-09-07 15:04 GMT+02

Re: Services, start levels, and waiting

David, I note that the use of an @Requirement leads to a Require-Capability in the manifest. In one case, I need to consume a service which is registered by a boring old Activator class in a bundle I do not control, and which does not have the corresponding Provide-Capability. I haven't seen a wiri

Re: Services, start levels, and waiting

So, the good news is that I read the spec, I followed you hints, and I converted a simple bundle of mine from blueprint to DS. The bad news is that Karaf 4.0.1 was unable to start up with a combination of aries-blueprint and scr enabled. I am going to see if the Karaf folks can give me a path thro

Re: Services, start levels, and waiting

> On Sep 5, 2015, at 5:47 PM, Benson Margulies wrote: > > On Sat, Sep 5, 2015 at 5:26 PM, David Jencks > wrote: >> >>> On Sep 5, 2015, at 5:08 PM, Benson Margulies wrote: >>> >>> On Sat, Sep 5, 2015 at 4:56 PM, David Jencks wrote: > On Sep 5, 2015, a

Re: Services, start levels, and waiting

On Sat, Sep 5, 2015 at 5:26 PM, David Jencks wrote: > >> On Sep 5, 2015, at 5:08 PM, Benson Margulies wrote: >> >> On Sat, Sep 5, 2015 at 4:56 PM, David Jencks wrote: >>> On Sep 5, 2015, at 3:09 PM, Benson Margulies wrote: On Sat, Sep 5, 2015 at 1:54 PM, David Jencks wrote

Re: Services, start levels, and waiting

On Sat, Sep 5, 2015 at 4:56 PM, David Jencks wrote: > >> On Sep 5, 2015, at 3:09 PM, Benson Margulies wrote: >> >> On Sat, Sep 5, 2015 at 1:54 PM, David Jencks wrote: >>> I’d suggest ditching blueprint and using ds. >> >> I might, except ... >> >> 1) CXF has a blueprint integration, and not a DS

Re: Services, start levels, and waiting

> On Sep 5, 2015, at 3:09 PM, Benson Margulies wrote: > > On Sat, Sep 5, 2015 at 1:54 PM, David Jencks wrote: >> I’d suggest ditching blueprint and using ds. > > I might, except ... > > 1) CXF has a blueprint integration, and not a DS integration. What does this integration do? IIRC bluepri

Re: Services, start levels, and waiting

On Sat, Sep 5, 2015 at 1:54 PM, David Jencks wrote: > I’d suggest ditching blueprint and using ds. I might, except ... 1) CXF has a blueprint integration, and not a DS integration. 2) Can you suggest a DS tutorial that does not lead straight into a maze of twisty passages related to BND versus

Re: Services, start levels, and waiting

On Sat, Sep 5, 2015 at 1:33 PM, Benson Margulies wrote: > org.apache.aries.blueprint.synchronous=true Unfortunately for me, I see that org.apache.aries.blueprint.synchronous=true is already in the default config.properties, so I'm puzzled.

Services, start levels, and waiting

So, At start-level 75, I have some bundles that register some services. But, of course, it takes a moment for them to start. Meanwhile, at start level 80, I have a bundle that uses blueprint to inject a list of all these services. I find that it starts before all the services are on-board. Is or