|
|
|
Re: Service Activation (Bundle-ActivationPolicy: lazy) [message #127143 is a reply to message #127093] |
Fri, 06 March 2009 18:44 |
Simon Kaegi Messages: 381 Registered: July 2009 |
Senior Member |
|
|
> To make it possible, I will register bundle/service implementation on its
> activation class, referencing by interface name (in another bundle).
>
> Is this a good idea?
That sounds fine however in that case you shouldn't bother with a lazy
bundle-activation policy and just ensure that your bundles are properly
started. Another approach worth looking at is to use Declarative Services.
"Emilio Numazaki" <mediasonic.l@gmail.com> wrote in message
news:5da98ede646ea6bd18944e5853986c56$1@www.eclipse.org...
> Hi Simon, first of all, thank you for your help
>
> I've tested what you told and it worked.
>
> But now I have another issue.
>
> My service interface and its implementation is in a separete bundle.
>
> In this case, what really matter is just its implementation, not the
> interface itself.
>
> How do I workaround this?
>
> My idea is to have a service interface bundle and many service
> implementation bundles for that set of interfaces, doing this, I can have
> multiple implementations that can be replaced without code change. I'll
> have just one implementation per solution but it can be switched easilly.
>
> To make it possible, I will register bundle/service implementation on its
> activation class, referencing by interface name (in another bundle).
>
> Is this a good idea?
>
> Thanks!
>
>
>
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.01551 seconds