Re: [osgi-dev] bundle symbolic name

Hi Ali, On Wed, 2018-11-07 at 06:53 +0300, Ali Parmaksız via osgi-dev wrote: > Hi all, > This is a basic question. But i want to ask you why symbolic name is > needed? > Then i think that it is about bundle installation, bundle:install > command > is sometihng like that: > bundle:install

Re: [osgi-dev] Declarative services and optional imports

Hi Ray, On Tue, Nov 21, 2017 at 4:34 PM, Raymond Auge wrote: > Hey Robert, > > We had the same use case and solved it the following way: > > Given your component which has the optional import package (doesn't matter > how it's used): > > import com.liferay.demo.foo.Foo;

Re: [osgi-dev] Declarative services and optional imports

services do not yet support this but it would be a very > valuable feature as it allows to handle optional imports without any class > loading magic on the user side. +1 Robert > > Christian > > 2017-11-21 14:53 GMT+01:00 Robert Munteanu via osgi-dev > <osgi-dev@mail.osgi.org&

Re: [osgi-dev] Declarative services and optional imports

Hi Tim, On Tue, Nov 21, 2017 at 3:47 PM, Timothy Ward wrote: > Hi Robert, > > From the code snippet it looks as though you aren’t using the standard > annotations (OPTIONAL_UNARY isn’t one of the enum values). If you want > support for non-standard annotations then you’ll

Re: [osgi-dev] Declarative services and optional imports

Hi Carsten, On Tue, Nov 21, 2017 at 3:50 PM, Carsten Ziegeler wrote: > Hi, > > if I understand you correctly you have an optional package import to the > package providing BarService? Yes, that is correct. > In that case your class SomeComponent can't be loaded if that

[osgi-dev] Declarative services and optional imports

Hi, I have an SCR component that references a service, with 0...1 cardinality. That service is part of an optional import. The aim is that if the package is available at runtime, the reference is bound, otherwise not, but the component functions without it, e.g. @Component public class