Bugzilla – Full Text Bug Listing
| Summary: | Please support the OSGi HTTP Service | ||
|---|---|---|---|
| Product: | [RT] Virgo | Reporter: | Ric Klaren <ric.klaren> |
| Component: | unknown | Assignee: | Chris Frost <eclipse> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | devel, eclipse, glyn.normington, norbert.wirges |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Ric Klaren
Hi, It would be quite easy to get HTTP Service support by deploying Jetty on top of the Kernel. There is information on it here, http://wiki.eclipse.org/Jetty/Feature/Jetty_OSGi#OSGi.27s_HttpService_via_equinox_servlet_bridge This may well happen in the future but it isn't that high on our priorities as we already support Gemini Web with Tomcat and will have full Jetty support shortly. I have had a quick look over the Pax Web site as I'm not familiar with their Extensions mechanism and I couldn't find much mention on it, I probably just went straight past it but could you please provide another link if you can. Finally, what is your objection to Snaps, it would be interesting to know in case we can get some requirement from your use case. Thanks, Chris. (In reply to comment #1) > It would be quite easy to get HTTP Service support by deploying Jetty on top of > the Kernel. There is information on it here, > http://wiki.eclipse.org/Jetty/Feature/Jetty_OSGi#OSGi.27s_HttpService_via_equinox_servlet_bridge But would that integrate with the web bundle? Or just provide another http server + port ? > This may well happen in the future but it isn't that high on our priorities as > we already support Gemini Web with Tomcat and will have full Jetty support > shortly. > > I have had a quick look over the Pax Web site as I'm not familiar with their > Extensions mechanism and I couldn't find much mention on it, I probably just > went straight past it but could you please provide another link if you can. Various bits are linked from this page: http://wiki.ops4j.org/display/paxweb/Http+Service+Extensions > Finally, what is your objection to Snaps, it would be interesting to know in > case we can get some requirement from your use case. a) vendor specific unless I missed something. (although pax web extensions would also be vendor specific) b) branded as prototype. c) More 'magic' than HTTP service. Magic is nice until it breaks. The OSGi HTTP service does exactly what we need and nothing more, supply a Servlet to our web bundle so we don't need to have a direct dependency between the web bundle and that other bundle. The pax web stuff would be some icing on the cake that could be useful in the future. We're already pretty pluggable with the use of wicket, so snaps feels heavy. On another note, DM Server / Virgo is a web server build on OSGi but does not support the standard OSGi HTTP Service? Cheers, Ric Hi, OK, your comments about Snaps are fair, especially about it being a prototype. I'm no expert on the Jetty support but I'm learning fast. When you talk about web bundles do you mean 'Web Application Bundles' as defined in the OSGi Web Applications spec. If so then the OSGi HTTPService isn't meant to support/integrate with that. In order to get support for Web Bundles you would need to use something like Virgo, Gemini Web or Jetty. All are OSGi based and provide implementations of OSGi Web Applications. If you just mean normal bundles that happen to do something with a Servlet, then yes OSGi HTTPService will do what you want and I'm afraid Virgo doesn't provide support for it out the box but it's very easy to drop an implementation in. Virgo aims to be an enterprise application server and the HTTPService is quite basic. Chris. (In reply to comment #3) > When you talk about web bundles do you mean 'Web Application Bundles' as > defined in the OSGi Web Applications spec. If so then the OSGi HTTPService > isn't meant to support/integrate with that. Indeed I meant Web Application Bundle. Aha, I more or less assumed that those two could go hand in hand. At least at first sight they don't seem to exclude each other. > If you just mean normal bundles that happen to do something with a Servlet, > then yes OSGi HTTPService will do what you want and I'm afraid Virgo doesn't > provide support for it out the box but it's very easy to drop an implementation > in. But it would appear on a different port I guess (since it cannot share the tomcat instance from virgo)? So we'd have to move our web application bundle to use the HTTP Service and then plug everything together. > Virgo aims to be an enterprise application server and the HTTPService is > quite basic. Indeed, that's why I mentioned the pax web stuff. Well this makes the feature request kindoff redundant at least running the two next to eachother feels ugly. It's either Web Application Bundle and Snaps. Or OSGi http service (or extension thereof). Thank you for the clarification. Cheers, Ric Hi, Virgo comes in two parts, a kernel and a web server that is built on top of the kernel. The Kernel has no web support at all but it does give you the deployment model, serviceability etc... It would seem a sensible approach for you to deploy the HTTP Service of your choice on the Kernel and go from there. This way there will be no clashes with Tomcat as it won't be there. The Kernel can be downloaded from the same place as the Virgo Web Server. http://www.eclipse.org/virgo/download/ Chris. (In reply to comment #5) > Virgo comes in two parts, a kernel and a web server that is built on top of the > kernel. The Kernel has no web support at all but it does give you the > deployment model, serviceability etc... It would seem a sensible approach for > you to deploy the HTTP Service of your choice on the Kernel and go from there. Thanks for the pointer. We had already seen the kernel (the DM Server variant) and tried it out. It would indeed be an approach to use the kernel. Pity is that we'd still need full virgo for STS integration (afaik STS does not work with the kernel, unless this recently changed). Cheers, Ric I have logged bug 331101 to add Virgo Kernel support to the Virgo tooling, but please note that there is a simple workaround documented in the bug. (In reply to comment #7) > I have logged bug 331101 to add Virgo Kernel support to the Virgo tooling, but > please note that there is a simple workaround documented in the bug. Ah nice, I was not aware of that trick :) thanks! As per the discussion in [virgo-dev] there are several alternatives available for this request and considering that this enhancement request will be closed. http://dev.eclipse.org/mhonarc/lists/virgo-dev/msg00488.html (In reply to comment #9) > As per the discussion in [virgo-dev] there are several alternatives available > for this request and considering that this enhancement request will be closed. > > http://dev.eclipse.org/mhonarc/lists/virgo-dev/msg00488.html Hi, Yesterday We have deployed Pax Web 0.8.0 over Virgo Jetty Server, enabling HttpService for Jetty 7.3 I you want more info, mail me to devel@thingtrack.com A recent forum thread on this topic: http://www.eclipse.org/forums/index.php?t=msg&th=206189&start=0&S=3a21abc1f2730a7094a73b13899b5b97 |