User: jules_gosnell Date: 02/02/22 15:54:31 Modified: jetty README Log: move some stuff into FAQ Revision Changes Path 1.11 +2 -36 contrib/jetty/README Index: README =================================================================== RCS file: /cvsroot/jboss/contrib/jetty/README,v retrieving revision 1.10 retrieving revision 1.11 diff -u -r1.10 -r1.11 --- README 21 Feb 2002 02:03:57 -0000 1.10 +++ README 22 Feb 2002 23:54:31 -0000 1.11 @@ -40,44 +40,10 @@ (java:/comp/env) etc. -DEVELOPMENT ------------- - -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. - -RUNNING --------- - -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. If you hit localhost:8080/ with your -browser, don't expect anything to be there, unless you have deployed -it yourself. If you haven't you will see a 404 - DO NOT BE ALARMED, -THIS IS CORRECT BEHAVIOUR. - -CONFIGURATION -------------- -The Jetty MBean is configured via META-INF/jboss-service.xml in -jetty-plugin.sar. - -The proprietary aspects of Jetty and webapps may be configured in -this jboss-service.xml and WEB-INF/jetty-web.xml respectively. - -In both cases, the format is an XML veneer over Jetty's native -Java API, so have your JavaDoc to hand - for further info see -jetty.mortbay.org. - -The non-proprietary parts are configurable through the standard J2EE -webapp descriptors. - Enjoy, -Jules ([EMAIL PROTECTED]) +Jules ([EMAIL PROTECTED]) 21/02/2002 +
_______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
