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.
Difference between revisions of "Jetty/HowTo/Using Jetty with Eclipse"
(New page: {{Jetty Howto | introduction = Jetty can be used in a variety of ways when developing in Eclipse. }} == WTP Style Usage == One generally problematic mechanism that people use is the WTP...) |
m |
||
| Line 1: | Line 1: | ||
{{Jetty Howto | {{Jetty Howto | ||
| − | | introduction = | + | | introduction = You can use Jetty in a variety of ways when developing in Eclipse. |
}} | }} | ||
| − | == WTP Style | + | == WTP Style Use == |
| − | + | A problematic mechanism is the WTP style approach to webapp development. Under certain circumstances this works for certain people and if it does, great, enjoy. Here is a link to a [[Jetty_WTP_Plugin|Jetty WTP Plugin]] that Angelo Zerr contributed. | |
| − | + | == Embedded Use == | |
| − | + | The embedded approach is an often used mechanism for developing in Eclipse. This strategy involves writing a small main method that starts Jetty and deploys your servlets programmatically. You can control the starting and stopping of your webapp through normal runtime measures. | |
| − | + | == Testing Use == | |
| − | + | You can use Jetty with JUnit or the like, where in @Before and @After there is a starting and stopping of a Jetty server. This is a popular approach to developing in Eclipse, and one that we employ heavily. If you're interested in this approach, look through the unit tests for things like jetty-server and jetty-client for a wealth of examples. Also see the [http://download.eclipse.org/jetty/stable-7/xref/org/eclipse/jetty/embedded/package-summary.html embedded-examples project] for a number of simple examples in common usage scenarios. | |
| − | + | }} | |
Revision as of 17:11, 11 August 2011
Introduction
You can use Jetty in a variety of ways when developing in Eclipse.
WTP Style Use
A problematic mechanism is the WTP style approach to webapp development. Under certain circumstances this works for certain people and if it does, great, enjoy. Here is a link to a Jetty WTP Plugin that Angelo Zerr contributed.
Embedded Use
The embedded approach is an often used mechanism for developing in Eclipse. This strategy involves writing a small main method that starts Jetty and deploys your servlets programmatically. You can control the starting and stopping of your webapp through normal runtime measures.
Testing Use
You can use Jetty with JUnit or the like, where in @Before and @After there is a starting and stopping of a Jetty server. This is a popular approach to developing in Eclipse, and one that we employ heavily. If you're interested in this approach, look through the unit tests for things like jetty-server and jetty-client for a wealth of examples. Also see the embedded-examples project for a number of simple examples in common usage scenarios.
}}