User: jules_gosnell Date: 02/02/22 15:53:17 Modified: jetty FAQ Log: a bit more content Revision Changes Path 1.2 +108 -23 contrib/jetty/FAQ Index: FAQ =================================================================== RCS file: /cvsroot/jboss/contrib/jetty/FAQ,v retrieving revision 1.1 retrieving revision 1.2 diff -u -r1.1 -r1.2 --- FAQ 21 Feb 2002 02:03:57 -0000 1.1 +++ FAQ 22 Feb 2002 23:53:17 -0000 1.2 @@ -1,8 +1,15 @@ + +What is Jetty? +------------- + +A pure Java, HTTP1.1 httpd, Servlet 2.3 & JSP 1.2 WebContainer. In +short an elegant solution to serving static and dynamic web +content. See jetty.mortbay.org for more information. + + Why would I want to use Jetty instead of Tomcat/Catalina? ---------------------------------------------------------- -<DISCLAIMER - don't believe any of this> - Tomcat and Jetty's missions are very different. Tomcat's is to define the standard behaviour of a J2EE-compliant web-container. Jetty's is to deliver this behaviour in as fast, lightweight, and embeddable @@ -21,54 +28,124 @@ Take your pick. + Will I have trouble moving my WebApp from Tomcat to Jetty --------------------------------------------------------- -Hopeful +Hopefully, you should experience no difference. The two provide +implementations of the same APIs and both are tested against +jakarta-watchdog, a testsuite of around 400 cases, to ensure +compliance. If, by mischance, you do happen to come across a +difference in behaviour between the two, mail [EMAIL PROTECTED] with a clear and specific explanation of +this difference and the Jetty development team will do their best to +resolve it. -Virtual Hosts -------------- -<put Greg's solution here> +How do I run the Jetty integration? +----------------------------------- + +Just start JBoss3. Jetty should deploy from the jetty-plugin.sar. The +HTTP server will be on 8080 by default. This and other proprietary +features are configurable in jboss-service.xml which you will find in +jetty-plugin.sar. Unpack it, make your changes, repack it and copy it +back whence you found it. JBoss will notice, reload and restart Jetty +with it's new configuration. Alternatively, for more ephemeral +alterations you can use the JMX Agent on 8082. + + +OK, I'm up and running, but I get a 404 when I hit 'localhost:8080/' +-------------------------------------------------------------------- + +Currently, JBoss comes with no webapps preinstalled, so starting it up +and hitting localhost:8080/ will result in your receiving a "404 Not +Found" error. This is NOT a problem with your installation. It IS +correct behaviour. If you want to see something there deploy +something. + + +How do I deploy a naked WAR to the '/' context +---------------------------------------------- + +When I deploy my app foo.war to JBoss, it gets installed at /foo. I +want it at /. + +You have two choices. + +1. The standard J2EE way - wrap your .war in an .ear and in the .ear's +application.xml you can specify the required context. +2. The proprietary JBoss extension - put a jboss-web.xml into your +.war's WEB-INF directory and specify the context root in that. -SSL ----- + +How do I configure the Jetty Service ? +-------------------------------------- + +Configuration for a JettyService instance may be found in +jetty-plugin.sar/META-INF/jboss-service.xml. + +Proprietary WebApp specific configuration may be done in +e.g. my.war/WEB-INF/jetty-web.xml. + +The ConfigurationElement in jboss-service.xml and the contents of +jetty-web.xml are written in a very XML veneer over Jetty's java API, +so have your JavaDoc to hand - for further info see jetty.mortbay.org. + + +I want to use Virtual Hosts +--------------------------- + +Virtual hosts are an area currently not (AFAIK) addressed by the J2EE +spec (1.3). There is an intention within the JBoss team to provide a +proprietary extension to provide this functionality. While this is +being worked out the interim solution is to go around JBoss and talk +directly to Jetty via the jetty-web.xml file in your .war's WEB-INF +directory. + +Try putting something like this in there: + + <put Greg's solution here> + + +I want to use SSL +----------------- <We need a link to Mortbay here> -Apache -------- +I want to integrate JBoss/Jetty with Apache (or another WebServer) +------------------------------------------------------------------ -<another link to mortbay here> +<another link to Mortbay here> -404 on / --------- +I want to use JAAS +------------------ -no worries - you haven't deployed anything yet - have you ? +JAAS support is configurable across the JettyService instance via an +attribute in jboss-service.xml (see above), or via localhost:8082 -Configuration --------------- +I want to run on 80, not 8080 +----------------------------- -EITHER - jetty-plugin.sar/META-INF/jboss-service.xml -OR - my.war/WEB-INF/jetty-web.xml +<another link to Mortbay> -JAAS ----- +Development +------------ -Look in jboss-service.xml +There is a 'devel' target in the build.xml which should rebuild and +deploy the plugin then (perhaps) run the WebIntergration test +suite. You need a JBoss up and running. Where can I go for Jetty help? ------------------------------ [EMAIL PROTECTED] +www.jboss.org/forums/????? Who is the author/maintainer of Jetty ? @@ -81,3 +158,11 @@ -------------------------------------------------------------- [EMAIL PROTECTED] + + + + +Enjoy, + + +Jules (21/02/2002)
_______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
