Contact the core Jetty developers at
www.webtide.com
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
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
DOCUMENTATION: Jetty 6 - this wiki. Jetty 7 - at Eclipse. Jetty8 - at Eclipse. Jetty 9 - at Eclipse.
Skip to end of metadata
Go to start of metadata
You are viewing an old version of this page. View the current version.
Compare with Current ·
View Page History
Java Micro Edition - Connected Device Configuration
Jetty 6 may be run on a JVM that supports JME Connected Device Configuration (CDC), such as the j9 VM from IBM.
To run on ME, you must:
- Not use XML, as a SAX parser is not available. This means that you cannot directly use webapplications
with web.xml nor jetty.xml to configure the server. - Not use NIO connectors. Use the SocketConnector instead.
- Write a configuration class similar to the examples in the examples/embedded module.
- Configure your own class path to include
- servlet-api.jar
- jetty-util.jar
- jetty.jar
- your configuration class(es).
An example of running the OneHandler example with IBMs J9 is
NOTE! It appears that J9 is a superset of CDC. JVMs such as jbed with a strict CDC
implementation appear to need some patches to Jetty to remove some 1.4 language
features. These patches will soon be available in the patches directory.
Labels