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/FAQ"
Line 19: | Line 19: | ||
{{Jetty FAQ | {{Jetty FAQ | ||
| question = Is Jetty production ready? | | question = Is Jetty production ready? | ||
− | | answer = | + | | answer = Yes. Since 1995, [http://docs.codehaus.org/display/JETTY/Jetty+Powered Jetty powers] hundreds of thousands of websites, serving millions of users and is embedded in thousands of products and projects. |
}} | }} | ||
{{Jetty FAQ | {{Jetty FAQ | ||
| question = Who uses Jetty? | | question = Who uses Jetty? | ||
− | | answer = | + | | answer = Jetty has a huge variety of users: |
+ | * Large clusters, such as the [http://developer.yahoo.net/hadoop/ Yahoo Hadoop Cluster] | ||
+ | * Cloud computing, such as the [http://code.google.com/appengine/ Google AppEngine] | ||
+ | * SaaS, such as [http://www.zimbra.com/ Yahoo! Zimbra] | ||
+ | * Application Servers, such as [http://geronimo.apache.org/ Apache Geronimo] | ||
+ | * Frameworks, such as [http://code.google.com/webtoolkit/ GWT] | ||
+ | * Tools, such as the [http://www.eclipse.org/ Eclipse IDE] | ||
+ | * Devices, such as [http://code.google.com/p/i-jetty/ phones] | ||
+ | See the [http://docs.codehaus.org/display/JETTY/Jetty+Powered Jetty Powered] page for more exemplar users. | ||
+ | |||
}} | }} | ||
{{Jetty FAQ | {{Jetty FAQ | ||
| question = Why use Jetty? | | question = Why use Jetty? | ||
− | | answer = | + | | answer = Some of the reasons to use Jetty over other available options are: |
+ | * Jetty is Open source with a commercially usable license. | ||
+ | * Jetty has a small foot print, yet is full featured and standards based. | ||
+ | * Jetty is flexible and extensible, so that if your application/deployment is not a standard webapp, Jetty can easily be customized. | ||
+ | * Jetty provides asynchronous HTTP handling within the safe standard servlet API model, without the need to program at the asynchronous IO level. | ||
+ | * Jetty has an innovative, responsive and approachable developer community. | ||
+ | See also a [http://www.webtide.com/choose/jetty.jsp Comparative Analysis with Tomcat]. | ||
}} | }} | ||
− | |||
− | |||
{{Jetty FAQ | {{Jetty FAQ | ||
Line 42: | Line 55: | ||
{{Jetty FAQ | {{Jetty FAQ | ||
− | | question = How do I | + | | question = How do I ask a question? |
− | | answer = You can get some help from the Jetty community by posting a question to the jetty-users@eclipse.org mailing list. When posting, please be sure to | + | | answer = You can get some help from the Jetty community by posting a question to #jetty on irc.freenode.org or to the jetty-users@eclipse.org mailing list. When posting, please be sure to have available as a minimum the following information: |
− | # Jetty version | + | # Jetty version |
− | # Browser version | + | # Browser version |
# OS platform | # OS platform | ||
# JVM version | # JVM version | ||
# Command line | # Command line | ||
+ | # Full stack trace of any exceptions | ||
If your problem involves a complex webapp, please try and provide us with just a small webapp instead that also demonstrates the problem. | If your problem involves a complex webapp, please try and provide us with just a small webapp instead that also demonstrates the problem. | ||
Debug logs, packet traces from tools such as ethereal or copies of the HTTP dialog as captured by tools such as Firefox "Live HTTP Headers" are always useful. | Debug logs, packet traces from tools such as ethereal or copies of the HTTP dialog as captured by tools such as Firefox "Live HTTP Headers" are always useful. | ||
+ | }} | ||
− | + | {{Jetty FAQ | |
− | + | | question = How do I know which version of Jetty I am running? | |
− | + | | answer = Locate the start.jar in your distribution. Then use the "--version" flag: | |
+ | java -jar start.jar -- version | ||
}} | }} | ||
− | |||
{{Jetty FAQ | {{Jetty FAQ | ||
Line 66: | Line 81: | ||
}} | }} | ||
+ | {{Jetty FAQ | ||
+ | | question = Is Jetty 7 a drop in replacement for Jetty 6? | ||
+ | | answer = No, while Jetty 7 has very much the same architecture as Jetty 6, there are packaging changes and other minor tweaks between the versions. Also, the Jetty 7 milestones are not as fully featured as Jetty 6 in terms of third party integrations being available by default with the distribution bundle. Please see the [[Jetty/Getting_Started#Upgrades|Upgrades section of our Getting Started documentation]]. | ||
+ | }} | ||
− | == Jetty | + | |
+ | == Developing with Jetty == | ||
{{Jetty FAQ | {{Jetty FAQ | ||
− | | question = How do I | + | | question = How do I get started? |
− | | answer = | + | | answer = See the [[Jetty/Starting|Getting Started]] guide. |
− | + | ||
}} | }} | ||
{{Jetty FAQ | {{Jetty FAQ | ||
− | | question = | + | | question = Are Maven 2 artifacts available? |
− | | answer = | + | | answer = Yes, Jetty is developed with Maven and artefacts are available at |
+ | * http://repo2.maven.org/maven2/org/eclipse/jetty | ||
}} | }} | ||
− | |||
{{Jetty FAQ | {{Jetty FAQ | ||
− | | question = | + | | question = What JARs do I need to run Jetty. |
− | | answer = | + | | answer = The core of Jetty has no external dependencies other that the servlet-api. See the [[Jetty/Reference/dependencies|Jetty Dependencies]] reference. |
− | + | ||
}} | }} | ||
+ | |||
+ | |||
+ | |||
+ | |||
== Others == | == Others == |
Revision as of 02:10, 27 July 2009
Contents
- 1 General
- 1.1 Why is it called Jetty?
- 1.2 Is Jetty production ready?
- 1.3 Who uses Jetty?
- 1.4 Why use Jetty?
- 1.5 What's the difference between Jetty from Mort Bay, Codehaus and/or Eclipse?
- 1.6 How do I ask a question?
- 1.7 How do I know which version of Jetty I am running?
- 1.8 Is commercial support available?
- 1.9 Is Jetty 7 a drop in replacement for Jetty 6?
- 2 Developing with Jetty
- 3 Others
General
Why is it called Jetty?
Mort Bay is at the heart of Balmain, Sydney NSW, Australia. A former working class suburb, now yuppieville in Sydney's close inner-west. Greg was living by Mort Bay when the company was formed, hence the company name.
Jetty was originally called IssueTracker (its original application) and then MBServler (Mort Bay SERVLet servER). Neither of these were much liked, so Jetty was finally picked as:
- it starts with a J
- the double tt in jetty:// looks a little like http://
- there is a jetty in the Mort Bay logo.
- there were no better suggestions.
Is Jetty production ready?
Who uses Jetty?
- Large clusters, such as the Yahoo Hadoop Cluster
- Cloud computing, such as the Google AppEngine
- SaaS, such as Yahoo! Zimbra
- Application Servers, such as Apache Geronimo
- Frameworks, such as GWT
- Tools, such as the Eclipse IDE
- Devices, such as phones
Why use Jetty?
- Jetty is Open source with a commercially usable license.
- Jetty has a small foot print, yet is full featured and standards based.
- Jetty is flexible and extensible, so that if your application/deployment is not a standard webapp, Jetty can easily be customized.
- Jetty provides asynchronous HTTP handling within the safe standard servlet API model, without the need to program at the asynchronous IO level.
- Jetty has an innovative, responsive and approachable developer community.
What's the difference between Jetty from Mort Bay, Codehaus and/or Eclipse?
How do I ask a question?
- Jetty version
- Browser version
- OS platform
- JVM version
- Command line
- Full stack trace of any exceptions
If your problem involves a complex webapp, please try and provide us with just a small webapp instead that also demonstrates the problem.
Debug logs, packet traces from tools such as ethereal or copies of the HTTP dialog as captured by tools such as Firefox "Live HTTP Headers" are always useful.
How do I know which version of Jetty I am running?
Is commercial support available?
Is Jetty 7 a drop in replacement for Jetty 6?
Developing with Jetty
How do I get started?
Are Maven 2 artifacts available?
What JARs do I need to run Jetty.
Others
Can you recommend some useful web developer tools?
These tools have nothing to do specifically with Jetty; they're just a list of tools we find useful in developing and diagnosing misbehaving webapps:
Browsers and GUI Tools
- Firefox - open source browser.
- Web Developer plugin for Firefox - all sorts of tools to help you develop and debug your HTML and CSS.
- Firebug plugin for Firefox - DOM inspector plus a lot more.
- Poster Plugin for Firefox - lets you do POSTs, GETs, PUTs, etc and see the results.
- DOM Inspector plugin for Firefox - DOM inspector.
- Venkman plugin for Firefox - legendary javascript debugger.
Http Protocol Analysis
- LiveHttpHeaders plugin for Firefox - shows you the HTTP dialog between browser and server.
- Tamper Data plugin for Firefox - shows you the HTTP dialog and allows you to modify
- Wireshark - network protocol analyzer.