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 "Jetty/Howto/Develop"

< Jetty‎ | Howto
Line 1: Line 1:
 
{{Jetty Howto
 
{{Jetty Howto
 
| introduction = Jetty Development can roughly be consider in two parts:
 
| introduction = Jetty Development can roughly be consider in two parts:
# Developing standard web applications that use only standard APIs, but that  
+
# Developing standard web applications that use only standard APIs, but that are deployed in jetty either for development and/or production.  These web applications may use some jetty APIs, but only as normal WEB-INF/lib libraries.
are deployed in jetty either for development and/or production.  These web applications may use some jetty APIs, but only as normal WEB-INF/lib libraries.
+
 
# Developing web applications that use jetty JETTY APIs for either embedded or closely integrated purposes. This style of development needs jetty jars on the class path during development and runtime
 
# Developing web applications that use jetty JETTY APIs for either embedded or closely integrated purposes. This style of development needs jetty jars on the class path during development and runtime
 
}}
 
}}

Revision as of 00:45, 5 February 2010



Introduction

Jetty Development can roughly be consider in two parts:

  1. Developing standard web applications that use only standard APIs, but that are deployed in jetty either for development and/or production. These web applications may use some jetty APIs, but only as normal WEB-INF/lib libraries.
  2. Developing web applications that use jetty JETTY APIs for either embedded or closely integrated purposes. This style of development needs jetty jars on the class path during development and runtime

Standard Web Application Development

Developing against Jetty APIs

Back to the top