If I had to start over with the design of OSGi there would be no bundle
activator, just DS components ... The activator was a mistake since it is a
singleton and I now sometimes wonder what we are smoking, forcing people to
handle their own service dependencies. DS's support services, service
factories, and more as well as fully handling service dependencies makes
services as lightweight as classes. With the DS annotations you can turn ay
class into a service (factory) whenever you want, not requiring any extra
setup. I found it amazing how light weight services became once I could do this.
You can control the life cycle of the component with config admin using managed
service (factories). Config admin can define/override service properties and
define which service dependencies are bound by setting the target filter.
With DS you do not need the dependency manager since DS handles deps for you.
Again, OSGi was not complete until DS was specified.
Kind regards,
Peters Kriens
Sent from my iPad
On 1 jun. 2013, at 00:10, bokie <[email protected]> wrote:
> I'm quite comfortable with OSGi and Felix but have I've never used
> Declarative Services. I've started reading up on the topic and started to
> ask my self some questions with respect to how I currently do things:
> - Are there any real benefits in using Declarative Services?
> - How does Declarative Services "integrate" with the the Configuration
> Admin?
> - How does Declarative Services "integrate" with the the Dependency Manager
>
>
>
> --
> View this message in context:
> http://apache-felix.18485.x6.nabble.com/declarative-Services-tp5003596.html
> Sent from the Apache Felix - Users mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
