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/Howto/Develop"
(New page: {{Jetty Howto | introduction = TBD }}) |
|||
| Line 1: | Line 1: | ||
{{Jetty Howto | {{Jetty Howto | ||
| − | | introduction = | + | | introduction = Jetty Development can roughly be consider in two parts: |
| − | + | # 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. | ||
| + | # 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 == | ||
Revision as of 00:44, 5 February 2010
Introduction
Jetty Development can roughly be consider in two parts:
- 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.
- 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