At OSGi DevCon / EclipseCon this month in Santa Clara, and one of the
things that the OSGi experts kept reiterating was to *not* program
directly to the OSGi API (anything from org.osgi.*). Instead they
recommended using your preferred flavor of declarative services such
as Spring dm, iPojo, or OSGi DS. See halfway down this interview with
Jeff McAffer for more on the topic:
http://java.dzone.com/articles/using-osgi-equinox-effectively.
With that in mind, I was hoping to learn more about the rationale
behind Jersey's OSGi activator. I understand the point of it - to
install the RuntimeDelegate according to the JAX-RS spec. But I would
argue that this could be left up to the Jersey developer to take care
of as part of the app initialization. Especially if the developer
wants to replace/modify the default implementation.
Hope this makes sense, and appreciate any insight here.
Eric