Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Virgo/Future"

(Jetty Support)
(Jetty Support)
Line 7: Line 7:
 
Note that Jetty support may be provided mostly in Virgo's sister project Gemini Web. The Tomcat-based Virgo Web Server integrates Gemini Web and a Jetty-based variant may do the same.
 
Note that Jetty support may be provided mostly in Virgo's sister project Gemini Web. The Tomcat-based Virgo Web Server integrates Gemini Web and a Jetty-based variant may do the same.
  
Jetty has existing [[Jetty/Feature/Jetty_OSGi|support for OSGi]] including RFC 66. After Jetty is bootstrapped in the OSGi framework, web bundles may be deployed directly to Jetty using the whiteboard pattern. A ContextHandler service must be registered with appropriate service properties
+
Jetty has existing [[Jetty/Feature/Jetty_OSGi|support for OSGi]] including RFC 66. After Jetty is bootstrapped in the OSGi framework, web bundles may be deployed directly to Jetty using the whiteboard pattern.
 +
 
 +
=== Deploying Web Bundles ===
 +
 
 +
A ContextHandler service must be registered with appropriate service properties. Presumably the bundle registering the service is the web bundle itself, although this is not clear from the Jetty documentation above.

Revision as of 03:46, 1 July 2010



This page notes design ideas for future Virgo features.

Jetty Support

Note that Jetty support may be provided mostly in Virgo's sister project Gemini Web. The Tomcat-based Virgo Web Server integrates Gemini Web and a Jetty-based variant may do the same.

Jetty has existing support for OSGi including RFC 66. After Jetty is bootstrapped in the OSGi framework, web bundles may be deployed directly to Jetty using the whiteboard pattern.

Deploying Web Bundles

A ContextHandler service must be registered with appropriate service properties. Presumably the bundle registering the service is the web bundle itself, although this is not clear from the Jetty documentation above.

Back to the top