Hello all, sorry for always comming back on the same subject, but tomorrow
is our deadline, and even we got some progress on the osgi front with spring
(we now have services and dependency injection working). Nothing seems to
work on the HttpService integration.
We tried almost everything to get equinox running inside a servlet
container. The documentation on equinox servlet bridge is almost inexistent.
We are not using their servletbridge since it starts the osgi container and
that is something we are doing in our code (following the sling approach)
What seems to be happening is that any service tracker registered to
HttpService never gets called, ever... We've seen this on the OsgiManager
class, and now we decided to drop our own little servlet bundle:
public class Activator implements BundleActivator {
private ServiceTracker httpServiceTracker;
public void start(BundleContext context) throws Exception {
httpServiceTracker = new HttpServiceTracker(context);
httpServiceTracker.open();
}
public void stop(BundleContext arg0) throws Exception {
httpServiceTracker.close();
httpServiceTracker = null;
}
private class HttpServiceTracker extends ServiceTracker {
public HttpServiceTracker(BundleContext context) {
super(context, HttpService.class.getName(), null);
}
public Object addingService(ServiceReference reference) {
HttpService httpService = (HttpService)
context.getService(reference);
try {
httpService.registerServlet("/dummy", new DummyServlet(),
null, null); //$NON-NLS-1$
} catch (Exception e) {
e.printStackTrace();
}
return httpService;
}
public void removedService(ServiceReference reference, Object
service) {
HttpService httpService = (HttpService) service;
httpService.unregister("/dummy"); //$NON-NLS-1$
super.removedService(reference, service);
}
}
}
Well, the adding servlet never gets called :(
Here how we start the felix container:
public void init() throws ServletException {
ServletContextResourceProvider rp = new
ServletContextResourceProvider(getServletContext());
Logger logger = new ServletContextLogger(getServletContext());
Map<Object, Object> props = loadProperties();
this.osl = new OSL(rp,props,logger);
this.delegatee = new HttpServiceServlet();
this.delegatee.init(getServletConfig());
super.init();
}
public class OSL implements BundleActivator {
private Felix felix;
private ReadWriteLock felixLock;
private ResourceProvider resourceProvider;
private Logger logger;
private BundleActivator httpServiceActivator;
public OSL(ResourceProvider rp, Map<Object, Object> props, Logger
logger){
this.resourceProvider = rp;
this.logger = logger;
List<BundleActivator> activators = new ArrayList<BundleActivator>();
activators.add(this);
activators.add(new BootstrapInstaller(logger,rp));
props.put(FelixConstants.SYSTEMBUNDLE_ACTIVATORS_PROP, activators);
Felix tmpFelix = new Felix(props);
try {
tmpFelix.start();
this.felix = tmpFelix;
} catch (Exception e) {
e.printStackTrace();
}
}
public void start(BundleContext context) throws Exception {
this.httpServiceActivator = new Activator();
this.httpServiceActivator.start(context);
}
As you can see, we are starting the Httpservice ourselves, we tried to not
do so and pack it with the other bundles, but the effect is the same (do not
call the addingservice)
After the complete startup we have these services:
System Bundle (0) provides:
---------------------------
org.osgi.service.startlevel.StartLevel
org.osgi.service.packageadmin.PackageAdmin
org.osgi.service.http.HttpService
So I guess the HttpService is up and running.
Is there anything else that we could do? Any other point to look at, replace
class, packaging format, anything please. Tomorrow if we don't present at
least one servlet (we needed at least the GWT-RPC working but one servlet
should do it), we may have to drop osgi for good, and that's something we
are really not willing to do :(
Regards
