[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [equinox-dev] Declarative Services vs Spring

I think that's intentional. With OSGi you always have to be aware that
the services you depend on might go away, and possibly come back again
later. That's the essence of OSGi - it's dynamic. In this context an
"immutable final service reference" is an oxymoron.

Spring lives in a comfortable static world where dependencies, once
supplied, will live for at least as long as the things that depend on
them. In OSGi, that kind of assumption is only really valid for
intra-bundle dependencies. DS on the other can handle dynamic
inter-bundle dependencies, which IMHO makes it much more powerful.

On the other hand Spring has much more to it than dependency
injection. It also has a number of very powerful libraries, eg for
developing DAOs using JDBC or O/R mappers, an AOP library, remoting
libraries, etc. Because Spring is wonderfully modular, you can use as
much or as little of it as you like (just like Eclipse!).

- Neil

On 3/1/06, Subbarao Meduri <mkv@xxxxxxxxxx> wrote:
> How does declarative services fare when compared with Spring framework in
> terms of its injection capabilities ? My apologies if this is already
> discussed on this forum.
>  Is there a reason why declarative services does not support constructor
> injection, for example ? It seems constructor injection is the only way to
> initialize a component that holds a immutable (final) service reference
> injected via its constructor.
>  Appreciate your thoughts.
>  Regards,
>  Subbarao
> _______________________________________________
> equinox-dev mailing list
> equinox-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/equinox-dev