I don't really recommend using the @OsgiService / @OsgiServiceProvider of
Pax-CDI.
The main reason is that if the bundles are not started in the correct
order, the bean validation will simply fail and your CDI app won't be
created at all.
I'd really recommend to look at the new annotations of
As with anything that uses the OSGi Service Registry properly, DS waits for a
service to be available before activating a component which uses that service.
This means that there is no configuration of startup order, and that there are
no points when the graph is incomplete assuming that:
a)
