If it is a bouncing problem, than you could also try to configure the behavior
using the property
ds.delayed.keepInstances=true
From the Apache Felix documentation:
Whether or not to keep instances of delayed components once they are not
referred to any more. The Declarative Services specificat
Sorry, but now I am a bit confused. Are you talking about the consumer or the
provider? @Reference is used to consume a service. If you want to create a
service instance via ConfigurationAdmin, that would be the producer side.
So some component needs to register your specific component instance
Hi,
not sure about your use case in detail, but it sounds like you either could use
the ConfigurationAdmin approach like I explained here:
http://blog.vogella.com/2017/02/13/control-osgi-ds-component-instances/
Probably that is what you have already tried.
But maybe the target reference proper
s correct, and either Tim misspoke or you misheard him.
The service should look like a big arrow pointing from the consumer to the
provider.
Neil
On Thu, Jun 28, 2018 at 2:57 PM, Fauth Dirk (AA-AS/EIS2-EU) via osgi-dev
mailto:osgi-dev@mail.osgi.org>> wrote:
Hi,
maybe a stupid question,
Hi,
maybe a stupid question, but I am preparing my slides for the Java Forum
Stuttgart about Remote Services, and remembered that Tim told me that my
diagrams are incorrect, as the triangle is directing into the wrong direction.
The big end should be on the producer side, while the cone end poi
ce.component-logger.support
(or section 112.3.12 in the PDF).
This section shows the recommended approach to obtaining a Logger instance in a
component.
Regards,
Neil
On Mon, Apr 9, 2018 at 11:56 AM, Fauth Dirk (AA-AS/EIS2-EU) via osgi-dev
mailto:osgi-dev@mail.osgi.org>> wrote:
H
Hi,
as with R7 the LogService is deprecated and instead the LoggerFactory should be
used, I wanted to start integrating the LoggerFactory in the Eclipse Platform.
But there is not much information about how the usage should be.
>From what I understand so far, the idea is similar to SLF4J that a
From my understanding the injection order should not be important in any way,
or said in a better way, you should never rely on it. Your component gets
satisfied once all required dependencies are resolved. So there is no component
instance until all references can be resolved and injected, ther
Hi,
IMHO it is a MINOR change because it is not a breaking change. ☺
With that change neither implementations of the Foo interface, nor classes that
extend the abstract Bar class will break.
Implementations of the Foo interface can still implement the doFoo() method and
by doing this override
