My company has used activators for quite some time, instead of annotations, due
to a perceived inability for the annotations to fit our needs.
I have cornered the use case that is reported to be the challenge. We have
services that are both aspects on services by their interfaces and also
void start() {
bc.registerService(EntitySynchronizer.class, this, null);
}
}
Doing so will register the aspect implementation also as an
EntitySynchronizer service.
Would this work around be fine for you ? let me know.
thanks
/pierre
On Thu, Jun 17, 2021 at 2:23 PM Steve Run
and also implements EntitySynchronizer. There are other
services (only a handful AFAIK) that whiteboard in EntitySynchronizers and
monitor the health of them by that interface.
From: Steve Runion
Sent: Thursday, June 17, 2021 5:18 AM
To: users@felix.apache.org
5 AM David Jencks
wrote:
> I’m used to the DS OSGI spec @Component annotation but I guess you are
> using the DM annotations and not DS?
>
> David Jencks
>
> > On Jun 16, 2021, at 1:57 PM, Steve Runion
> wrote:
> >
> > My company has used activators for q
4 matches
Mail list logo
