Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Jetty/Tutorial/EclipseRT-Jetty-Starter-Kit"
m (New page: {{Jetty Tutorial | introduction = This tutorial shows how to use the EclipseRT Jetty StarterKit. | details = == StarterKit Overview == Eclipse RT StarterKit is configured out of the bo...) |
m |
||
Line 10: | Line 10: | ||
* P2 support: simpleconfigurator, dropins reconciler, provisioning commands for the OSGi console | * P2 support: simpleconfigurator, dropins reconciler, provisioning commands for the OSGi console | ||
* slf4j, logback | * slf4j, logback | ||
+ | * Jetty-7: servlet-2.5, JSP-2.1, JMX, JNDI, JTA, Websocket and continuations... | ||
+ | Current download URL: http://download.eclipse.org/jetty/7.1.3.v20100526/dist/eclipse/ | ||
== On the command-line == | == On the command-line == |
Revision as of 14:56, 8 June 2010
{{Jetty Tutorial | introduction = This tutorial shows how to use the EclipseRT Jetty StarterKit.
| details =
Contents
StarterKit Overview
Eclipse RT StarterKit is configured out of the box with
- Equinox
- P2 support: simpleconfigurator, dropins reconciler, provisioning commands for the OSGi console
- slf4j, logback
- Jetty-7: servlet-2.5, JSP-2.1, JMX, JNDI, JTA, Websocket and continuations...
Current download URL: http://download.eclipse.org/jetty/7.1.3.v20100526/dist/eclipse/
On the command-line
Launch
The starter kit can be launched via the equinox native launcher or directly through java.
Jetty server configuration
The jetty server is configured via the etc/jetty.xml file.
Logging configuration
slf4j, logback: configured in etc/logback.xml
Upgrade and bundle management
Via P2 (link to the P2 console command controles.)
Dropins reconciler
It is possible to add bundles in the dropins folder. This is not a recommended practice.
J2EE support
- Web application can be dropped in the webapps folder.
- Jetty Context files can be defined in the contexts folder.
- Shared libraries between webapps can be placed inside lib/ext.
The resulting applications's classloaders behave in the same manner than in the traditional J2EE distribution of Jetty. Those web-applications and shared libraries don't have access to classes provided by OSGi bundles.