I'm currently writing a server-side app with OSGi+Equinox, perhaps these
items might be useful:
* Spring has better IoC and dependency injection than OSGi.
* Eclipse's extension system is not part of the OSGi standard, it
requires equinox (although there are rumors that it may be decoupled)
This gives you the following options:
* OSGi (plain)
* OSGi + Spring
* Equinox OSGi + Spring + Registry
* Equinox OSGi + Registry
In the last 2 options, you will be able to use Eclipse PDE to create
plugins and extensions.
Note that Services and Extensions/Extension Points are different and
somewhat complementary; Services are more code-oriented,
Extensions/Extension points are more data/metadata-oriented.
For a more in-depth article, look at
http://www.eclipsezone.com/articles/extensions-vs-services/
* Declarative Services in OSGi are strongly recommended, will make life
much easier. Same for Spring-OSGi.
* In terms of effort required, utilizing OSGi in Magnolia will be either
in the 4.0 or 5.0 timescale; while it is possible to use OSGi alongside
magnolia as an extension/plugin mechanism, for best results you will
want to convert magnolia to bundles and host it within an OSGi
environment completely.
* OSGi does provide you with an in-place update mechanism, but not a
policy.
HTH,
Tassos Bassoukos
P.S. I haven't written anything for magnolia, I just maintain 3
installations of it.
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------
