|
Re: HttpService workaround [message #660064 is a reply to message #660052] |
Wed, 16 March 2011 17:44 |
|
Hi,
There are various options depending on how much support you need. The Jetty distribution doesn't provide a HttpService, it's there to provide an alternative implementation of the OSGi Web Application Container Spec and is by no means as stable or tested as the Tomcat based one as we only recently added the Jetty option.
There is a HttpService for Jetty 7 that can be deployed on top of the Jetty WAB support, you can find it here if you want to play with it. http://repo1.maven.org/maven2/org/eclipse/jetty/osgi/jetty-h ttpservice/ It runs on top of the Jetty 7 Web Application Container.
If you only require a basic HttpService then their is one that comes with Equinox and is very simple to deploy on top of the Virgo Kernel distribution, simply add the servlet api bundle to the usr repository and drop org.eclispe.equinox.http in the pickup directory. This can of course be configured to start with the 'initialArtifacts' property as well. This has the benefit of being much more much more minimal.
Chris.
------------------------------------------------
Chris Frost, Twitter @cgfrost
Springsource, a divison of VMware.
|
|
|
|
|
|
|
Re: HttpService workaround [message #660201 is a reply to message #660187] |
Thu, 17 March 2011 10:37 |
|
The Virgo Jetty Server doesn't provide a HttpService either but you can get one with Jetty 7. It is available from Maven Central at the link I provided. The Equinox Bundles are still providing a HttpService based on Jetty 6, I don't know when/if they will provide the Jetty 7 one.
------------------------------------------------
Chris Frost, Twitter @cgfrost
Springsource, a divison of VMware.
|
|
|
Powered by
FUDForum. Page generated in 0.03720 seconds