Hi all,
osgi-jax-rs-connector works like a charm! Great simplification!
Though it seems that it is not automatically working with the tomcat version of virgo.
I was able to get it running by integrating the (meanwhile outdated ;) OSGi HttpService and a little "bridge bundle" that I created on my own. That bundle is a nearly empty WAB (Web Application Bundle) that simply registers the HttpServiceServlet (from org.eclipse.equinox.http.servlet) via web.xml.
But:
It all would be far easier if osgi-jax-rs-connector itself would be WABified. Wouldn't that be easily possible? I've seen that it only uses the HttpService in order to register its own servlet.
It even should be possible to create an additional (WAB) bundle that registers the jax-rs servlet. So if somebody is missing the HttpService in its (virgo) runtime he could then add the WAB.
Hi all, osgi-jax-rs-connector works like a charm! Great simplification!
Though it seems that it is not automatically working with the tomcat version of virgo. I was able to get it running by integrating the (meanwhile outdated ;) OSGi HttpService and a little "bridge bundle" that I created on my own. That bundle is a nearly empty WAB (Web Application Bundle) that simply registers the HttpServiceServlet (from org.eclipse.equinox.http.servlet) via web.xml.
But: It all would be far easier if osgi-jax-rs-connector itself would be WABified. Wouldn't that be easily possible? I've seen that it only uses the HttpService in order to register its own servlet. It even should be possible to create an additional (WAB) bundle that registers the jax-rs servlet. So if somebody is missing the HttpService in its (virgo) runtime he could then add the WAB.
Objections? Opinions?