private support for your internal/customer projects ... custom extensions and distributions ... versioned snapshots for indefinite support ... scalability guidance for your apps and Ajax/Comet projects ... development services from 1 day to full product delivery
You are viewing an old version of this page. View the current version.
Compare with Current ·
View Page History
OSGi Tips
As of release 6.1.5, Jetty ships with jar file manifests that include appropriate OSGi bundle information. This means that you can import the jetty jars into an OSGi framework and use them, for example, to build a HTTP service.
The jetty jars whose manifests include OSGi bundle information are:
- servlet-api-2.5.jar
- jetty-util.jar
- jetty.jar
- jetty-management.jar
- jetty-naming.jar
- jetty-plus.jar
- jetty-annotations.jar
- jsp-api-2.1.jar
- jsp-2.1.jar
Using jetty jars in Equinox
The jetty bundles mostly have dependencies amongst themselves (loosely in the order listed above), although the jetty-naming.jar and the the jsp jars do have external dependencies.
If you are using Equinox, it is quite easy to resolve these dependencies. Here's an Equinox config.ini file with all the external dependencies already setup up so that they will be loaded at start up time. If you place a copy of this file in your Eclipse plugins/configuration directory, you can start Equinox (assuming you're using the 3.3 distribution) with:
If you have put the config.ini file elsewhere, then start it like: