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/FAQ"
< Jetty
| Line 1: | Line 1: | ||
{{Jetty FAQ Section}} | {{Jetty FAQ Section}} | ||
| − | == | + | == General == |
| + | |||
| + | {{Jetty FAQ | ||
| + | | question = Why is it called Jetty? | ||
| + | | answer = Jetty was originally developed by Greg Wilkins of Mort Bay Consulting in 1995! | ||
| + | |||
| + | 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. | ||
| + | }} | ||
| + | |||
| + | {{Jetty FAQ | ||
| + | | question = Is Jetty production ready? | ||
| + | | answer = | ||
| + | }} | ||
| + | |||
| + | {{Jetty FAQ | ||
| + | | question = Who uses Jetty? | ||
| + | | answer = | ||
| + | }} | ||
| + | |||
| + | {{Jetty FAQ | ||
| + | | question = Why use Jetty? | ||
| + | | answer = | ||
| + | }} | ||
| + | |||
| + | |||
| + | |||
| + | {{Jetty FAQ | ||
| + | | question = What's the difference between Jetty from Mort Bay, Codehaus and/or Eclipse? | ||
| + | | answer = The latest releases of core jetty-7 and later are available from [http://www.eclipse.org/jetty/ Eclipse], which use the org.eclipse.jetty packaging. For versions 6 of Jetty, plus some jetty-7 components such as RPMs, Debs, Hightide, use [http://jetty.codehaus.org/ codehaus], which uses the org.mortbay packaging. For more information on this topic see [http://www.eclipse.org/about/jetty About Jetty]. | ||
| + | }} | ||
| + | |||
| + | |||
| + | |||
{{Jetty FAQ | {{Jetty FAQ | ||
| question = How do I submit a question? | | question = How do I submit a question? | ||
| Line 22: | Line 61: | ||
| − | |||
{{Jetty FAQ | {{Jetty FAQ | ||
| − | | question = | + | | question = Is commercial support available? |
| − | | answer = | + | | answer = Yes. See [http://www.webtide.com Webtide]. |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
}} | }} | ||
| + | |||
== Jetty Versions == | == Jetty Versions == | ||
| − | |||
| − | |||
| − | |||
| − | |||
{{Jetty FAQ | {{Jetty FAQ | ||
Revision as of 01:44, 27 July 2009
Contents
General
Why is it called Jetty?
Jetty was originally developed by Greg Wilkins of Mort Bay Consulting in 1995!
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?
Why use Jetty?
What's the difference between Jetty from Mort Bay, Codehaus and/or Eclipse?
The latest releases of core jetty-7 and later are available from Eclipse, which use the org.eclipse.jetty packaging. For versions 6 of Jetty, plus some jetty-7 components such as RPMs, Debs, Hightide, use codehaus, which uses the org.mortbay packaging. For more information on this topic see About Jetty.
How do I submit a question?
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 include as a minimum the following information:
- Jetty version 1
- Browser version 2
- OS platform
- JVM version
- Command line
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.
(1) If you are using a snapshot version, please look in your local maven repo for a maven-metadata-xxxx.xml file. The xxxx part is the name you have given the mortbay snapshot repo at http://jetty.mortbay.org/maven2/snapshot in your pom.xml. Report the snapshot number contained in it.
(2) Include this information if relevant to your problem.
Is commercial support available?
Yes. See Webtide.
Jetty Versions
How do I know which version of Jetty I am running?
Locate the start.jar in your distribution. Then use the "--version" flag:
java -jar start.jar -- version
Is Jetty 7 a drop in replacement for Jetty 6?
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 Upgrades section of our Getting Started documentation.
Are Maven 2 artifacts still available?
Yes, Jetty still supports our Maven based users to the same degree as previously. The location of artifacts has changed though.
Others
Can you recommend some useful web developer tools?
Yes!
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.