Re: [osgi-dev] @ConsumerType vs @ProviderType

Welcome to the club ;) I struggled with that myself for a long time. I think I finally got to understand it couple of years ago. Here is how I explained it during one of my talks: https://www.youtube.com/watch?v=hGNrZmr0zz8=youtu.be=1569 I hope this helps better than me trying to write it all

Re: [osgi-dev] [SCR] How to detect a missing configuration for a DS component

>From the top of my head configuration is by default optional but there was way to say that configuration is required. Is such cases if configuration is not provided you should get UNSATISFIED_CONFIGURATION On Tue, Apr 17, 2018 at 4:54 PM, Christian Schneider via osgi-dev <

Re: [osgi-dev] How to hint the resolver to pick a certain service provider

if the thing doesn’t exist, then you don’t want that > to prevent resolution of the bundle in OSGi. > > I hope that all makes sense. > > Unfortunately I don’t think this is really relevant to Christian’s > problem, though. > > Neil > > > On 17 Aug 2017, at 16:50, Mil

Re: [osgi-dev] How to hint the resolver to pick a certain service provider

Hi Christian, have you tried adding effective="..." to the annotations and then -resolve-effective: ... to bndrun file? Sorry for the dots but I never understood how to determine what the values should be to make given resolver ignore or enforce the requirement. I always play around with them

Re: [osgi-dev] Start Ordering in OSGi

Hi Peter, if I understand correctly (I must admit it's not immediately clear to me), you think of Aggregate State service as something that should be a general purpose service provided by OSGi implementation or some library. In another words, it's not something that developers need to implement

[osgi-dev] requirements capabilities and resolver for general purpose provisioning

Hi all, Is anyone aware of any attempt to use the requirements, repositories and resolver specs for anything other than provisioning OSGi runtime? It seams to me the specs are generic enough to be used in other scenarios. One example that comes to my mind is provisioning a telecommunication

Re: [osgi-dev] runtime bundle augmentation

here officially. > > If you want to try it maybe you could help me find a home for it. > > - Ray > > On Fri, Dec 16, 2016 at 12:22 PM, Milen Dyankov <milendyan...@gmail.com> > wrote: > >> Is there runtime alternative for bnd's `-augment`? >> >> Usec

[osgi-dev] runtime bundle augmentation

Is there runtime alternative for bnd's `-augment`? Usecase is say vendor of A provides proper bundle with "Require-Capability: X". There is bundle B which provides X but no one bothered to put "Provide-Capability" in it. Augmenting B in `bndrun` is tempting option to "properly" assemble a

Re: [osgi-dev] Component being activated twice?

Not sure why you decided to move the discussion back here but fine with me, at least I'm not the one highjacking the thread :) I agree with "well defined distros" but that only works for greenfield projects. There may be hundreds of variations of runtimes out there. Some vary basic examples: -

Re: [osgi-dev] notion of "provided" scope for build time resolver

not according to http://bnd.bndtools.org/chapters/825-instructions-ref.html :) On Wed, Nov 23, 2016 at 10:42 PM, Raymond Auge <raymond.a...@liferay.com> wrote: > -distro: is an existing bnd instruction implemented by Peter. > > - Ray > > On Wed, Nov 23, 2016 at 4:22 PM, Mil

[osgi-dev] notion of "provided" scope for build time resolver

I didn't want to highjack the "Component being activated twice?" thread so decided to start a new one. Regarding the "*-distro*" instruction - I don't seam to find any info about it. I assume this was simply an idea Ray proposed and not something that exist and need to be improved? Please correct

Re: [osgi-dev] Component being activated twice?

In this particular case removing scr from Karaf is OK because there is nothing in it that needs it. That would not be a universal solution though. Same thing with deploying through agent - works perfect in such experiment green field cases but that's likely not how one would deploy in big

Re: [osgi-dev] OSGi enRoute Maven Testers wanted ...

I ended up having: → mvn clean install [INFO] Scanning for projects... [INFO] [INFO] [INFO] Building osgi.enroute.examples.eval.bndrun 1.0.0-SNAPSHOT [INFO]

Re: [osgi-dev] The JPA spec bundle does not work with jpa 2.1

> > I agree with Christian that this should be clearly documented in a wiki > somewhere. Please someone, DO document this! I already moved this thread to my "Things about OSGi that you need to read at least 5 times before they start making sense" folder :) but for anyone not on this list, it

Re: [osgi-dev] Bundle resolution in BND

I'm sorry to respond without actually providing an answer but I couldn't help it. Least time (not so long ago) I asked myself similar question I ended up learning what NP-complete process is ;) And I'm still trying to make sense out of it ... 31 sie 2016 13:31 "Daghan ACAY"

Re: [osgi-dev] Where is the RFC and RFP list ?

Just as a side note https://github.com/buunguyen/octotree makes browsing the repo a bit less painful On Mon, Jul 4, 2016 at 4:17 PM, Raymond Auge wrote: > I have to agree with Cristiano. > > The issue may be fine on the RFP subdirectory, but on the RFC side it's >

Re: [osgi-dev] Java 9 / JSR 276 and OSGi plans

l > > Regards, > Neil > > > On 11 Mar 2016, at 12:44, Milen Dyankov <milendyan...@gmail.com> wrote: > > Hello, > > can someone please point me to some resource that describes the plans for > OSGi / JSR 276 interoperability? > > I'm sorry if this has been alr