declarative-services

I'm migrating an existing GWT app running on OSGi (Equinox) and Pax-web to use Declarative Services instead of programmatic Service Tracker. I'm using Pax-Web in Equinox. A WAR-based GWT application is loaded with no problems by PAX-WEB War extender, but you cannot have Declarative Services in this modus operandis. I successfully refactored all servlets out of the war and converted them into declarative OSGi services ( <provide interface="javax.servlet.Servlet"/> ). That way I got rid of all the messy ServiceTracker code and specific OSGi dependencies in the servlets. I further replicated all

Assuming I use OSGi Declarative Services and I have a service that have a number references with policy = dynamic... A - Mandatory unary. B - Mandatory unary. C - Mandatory multiple. D - Optional unary. E - Optional multiple. All references are available when my service starts. Is there any way to control what order bind is called in? I'd like to have B bind first and do something to each E that comes in, but I have no way of ensuring that B is bound before E. Yes, the more logical approach would be to let the service that represents B also bind to E and do whatever it should do, but I can't

I have written an OSGi bundle to use it in my eclipse 4 rcp application. The usage of the service works fine if I add the dependencies, register these service in my activator and inject it in my class. In activator IUserService service = new TestUserService(); context.registerService(IUserService.class.getName(), service, null); In my class @Inject IUserService service; service.getSth(); I read that using bundles via declarative services should be the better way. So changed my implementation. I created a component definition in my bundle to provide my service: <?xml version="1.0" encoding="UTF

I have services that need to be created on a per-configuration base, each of which relies on an external resource and thus should manage it's own lifcycle (i.e. (de)register the service). Thus implementing these as DS and let SCR spawn multiple instances does not work. One can implement a bundle that registers a ManagedServiceFactory to accomplish this task perfectly (see my previous post ). But as a consequence, if the factory depends on several other services, you need to start tracking those services and write a lot of glue code to get everything running. Instead I'd like to implement the