User: janb    
  Date: 02/02/19 21:53:51

  Modified:    jetty/src/etc README
  Removed:     jetty/src/etc demo.xml jetty.properties jetty.xml
                        webdefault.xml
  Log:
  Removed need for jetty.xml (all in jboss-service.xml) and webdefault.xml (ships 
within the org.mortbay.jetty.jar).
  
  Revision  Changes    Path
  1.5       +27 -18    contrib/jetty/src/etc/README
  
  Index: README
  ===================================================================
  RCS file: /cvsroot/jboss/contrib/jetty/src/etc/README,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- README    10 Sep 2001 23:52:05 -0000      1.4
  +++ README    20 Feb 2002 05:53:51 -0000      1.5
  @@ -1,32 +1,42 @@
   -----------------------------------------------------------------------
  +Using a custom webdefault.xml
  +-----------------------------------------------------------------------
  +As of JBoss 3.x, Jetty uses a standard webdefault.xml file by default.
   
  -Un*x users:
  +In order to override the webdefaults.xml shipped with Jetty, place
  +a customized webdefault.xml file into this directory, uncomment the
  +appropriate line in src/resources/jetty-plugin/META-INF/jboss-service.xml,
  +and then rebuild the Jetty JBoss Service Archive (jetty-plugin.sar) and
  +redeploy.
   
  -run ./run.sh in this dir.
   
  -If you are thinking of using the CGI Servlet you will want to 'chmod
  -+x jetty/cgi-bin/*' - for some reason the executable bit seems to get
  -lost in the [un]jarring process.
  +-----------------------------------------------------------------------
  +Customizing Jetty configuration
  +-----------------------------------------------------------------------
  +As of JBoss 3.x, essential Jetty configuration is placed within Jetty's
  +jboss-service.xml file instead of requiring a jetty.xml file. 
   
  -MS Users:
  +As shipped, the Jetty configuration fires up a listener on port 8080,
  +and sets up a standard HTTP request log in the JBoss log directory.
  +If you wish to specify an SSL listener, then uncomment the appropriate 
  +lines in src/resources/jetty-plugin/META-INF/jboss-service.xml,
  +rebuild and redeploy.
   
  -cd to ./jboss/bin and 'run.bat jetty'
  +If you REALLY NEED to customize Jetty further, place your custom Jetty
  +XML into a web-jetty.xml file in your WEB-INF/ directory of your war files.
   
  -(please send me the equiv run.bat for this dir)
  +DO NOT add webapps into the jboss-service.xml file, as these will not be visible to 
the JBoss deployment mechanism.
   
   -----------------------------------------------------------------------
  +MBeans
  +-----------------------------------------------------------------------
  +By default, Jetty will create MBeans for all listeners, contexts, log sinks etc. To 
view them, hit http://localhost:8082
   
  -For some Jetty doc and Demos run up JBoss-Jetty and hit:
  -
  -http://my-jboss-host:8080
  -
  -You can look around the MBeans running within Jetty by hitting :
  -
  -http://my-jboss-host:8082
   
  -and looking at the 'Jetty' links...
   
   -----------------------------------------------------------------------
  +Reporting problems
  +-----------------------------------------------------------------------
   
   Please post problems accordingly :
   
  @@ -38,11 +48,10 @@
   
   JBoss (everything else) related -> [EMAIL PROTECTED]
   
  ------------------------------------------------------------------------
   
   
  -Thanks for using JBoss-Jetty,
   
  +Thanks for using JBoss-Jetty,
   
   Jules (JBoss-Jetty maintainer) - [EMAIL PROTECTED]
   
  
  
  

_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to