[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [virgo-dev] Security in Virgo
- From: Ric Klaren <rklaren@xxxxxxxxxxx>
- Date: Thu, 25 Nov 2010 10:19:16 +0100
- Delivered-to: firstname.lastname@example.org
On 25 November 2010 09:55, Florian Waibel <fwaibel@xxxxxxxxxxxxxxxxx> wrote:
>>> BTW there is no enhancement bug for a HttpService in Virgo, but please raise one if you would like to. We already support Tomcat via Gemini Web and we are planning to support Jetty in the next release, so HttpService won't be high priority, but someone in the community may care to implement it.
>> Will do.
> Did you raise the enhancement bug?
I was under an assumption that a OSGi HTTP service could integrate
with an existing Web Application Bundle, but Christopher Frost pointed
out that this was not the case. So for my direct use case it does not
> It is also possible to "install" an HttpService into the user space. We did this to run RAP on an HttpService provided by
> Jetty on a bare Virgo Kernel installation .
That's indeed an option. Running the full virgo stack becomes a bit
heavy then. So we could use the virgo kernel and jetty/Pax Web or
whatever http service provider. Disadvantage is that afaik the kernel
does not work with STS. But maybe we could develop on full virgo and
deploy the virgo kernel. Although reasons to use Virgo become thin if
we use that route, many DM server/Virgo features are something we
> Here is the list of bundles we used in the RAP plan:
> Â Â Â Â<artifact type="bundle" name="org.mortbay.jetty.util" version="[6.1.23, 7.0.0)" />
> Â Â Â Â<artifact type="bundle" name="org.mortbay.jetty.server" version="[6.1.23, 7.0.0)" />
> Â Â Â Â<artifact type="bundle" name="org.eclipse.equinox.registry" version="[3.5.0, 4.0.0)" />
> Â Â Â Â<artifact type="bundle" name="org.eclipse.equinox.http.registry" version="[1.1.0, 2.0.0)" />
> Â Â Â Â<artifact type="bundle" name="org.eclipse.equinox.http.servlet" version="[1.1.0, 2.0.0)" />
> Â Â Â Â<artifact type="bundle" name="org.eclipse.equinox.http.jetty" version="[2.0.0, 3.0.0)" />
Thanks that saves some time figuring things out when we start to experiment :)
You might btw have a look at PAX Web
http://wiki.ops4j.org/display/paxweb/Pax+Web it has some extensions
that might be useful (and is built on jetty). I don't have handson
experience with it yet but in features it looks nice, YMMV.