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.
Difference between revisions of "Jetty/Feature/Jetty OSGi"
(New page: {{Jetty Feature | introduction = Jetty on OSGi consists of bootstrapping a standard jetty server from OSGi. It supports the deployment of traditional J2EE web-applications as well as web-a...) |
m |
||
| Line 9: | Line 9: | ||
| body = | | body = | ||
| − | + | == Architecture Overview == | |
| − | == Jetty OSGi bootstrapping == | + | === Jetty OSGi bootstrapping === |
A single bundle 'org.eclipse.jetty.osgi.boot' acts as an alternative to [[Jetty/Feature/Start.jar|Jetty's Start.jar]]. | A single bundle 'org.eclipse.jetty.osgi.boot' acts as an alternative to [[Jetty/Feature/Start.jar|Jetty's Start.jar]]. | ||
It wires up all the jetty jars that can be located. | It wires up all the jetty jars that can be located. | ||
| Line 25: | Line 25: | ||
== Deployment of web-applications via OSGi == | == Deployment of web-applications via OSGi == | ||
| − | == Support for RFC66 == | + | === Support for RFC66 === |
| − | == The OSGi service 'org.eclipse.jetty.server.handler.ContextHandler' == | + | === The OSGi service 'org.eclipse.jetty.server.handler.ContextHandler' === |
| − | == Extensions to RFC66 == | + | === Extensions to RFC66 === |
| − | + | == Architecture == | |
| − | == Detailed classloader tree == | + | === Detailed classloader tree === |
| − | == Injecting new server-wide features into jetty-osgi == | + | === Injecting new server-wide features into jetty-osgi === |
Support for jsp; | Support for jsp; | ||
Support for a different jndi implementation; | Support for a different jndi implementation; | ||
Revision as of 16:11, 29 November 2009
Contents
Introduction
Jetty on OSGi consists of bootstrapping a standard jetty server from OSGi. It supports the deployment of traditional J2EE web-applications as well as web-applications contained inside an OSGi bundle (RFC66).
The goal of Jetty on OSGi is to offer a migration path for traditional J2EE applications to run inside an OSGi container. It favors J2EE applications currently deployed on jetty: developers and IT administrators familiar with a jetty deployment will found the same folder structure and configuration files.
Jetty-on-OSGi also provides an SDK for Eclipse-PDE that supports the development and debugging of a mix of traditional web-applications and web-applications contained in an OSGi bundle: Jetty on OSGi SDK for Eclipse PDE.
Feature
Architecture Overview
Jetty OSGi bootstrapping
A single bundle 'org.eclipse.jetty.osgi.boot' acts as an alternative to Jetty's Start.jar. It wires up all the jetty jars that can be located. It locates the ${jetty.home} folder where the configuration files are located. It starts a jetty server according to these configuration files:
It locates a ${jetty.home} folder (or generate one by default) and starts a jetty server according to the jetty.xml file.
The classloader inside which the jetty server is executing is a mix of the OSGi classloader provided by the 'org.eclipse.jetty.osgi.boot' bundle and also the jars and folders found inside ${jetty.home}/lib/ext and ${jetty.home}/resources.
The jetty.xml provided by default in jetty will deploy all web-applications found inside the ${jetty.home}/webapps and will read the jetty context files found inside ${jetty.home/contexts}.
Deployment of web-applications via OSGi
Support for RFC66
The OSGi service 'org.eclipse.jetty.server.handler.ContextHandler'
Extensions to RFC66
Architecture
Detailed classloader tree
Injecting new server-wide features into jetty-osgi
Support for jsp; Support for a different jndi implementation;
Additional Resources
(optional) - links, additional references
(optional) - categor(ies) to use for this page. If blank, will use the template name as a default category Example: