User: salborini
  Date: 00/11/10 13:14:22

  Modified:    src/etc/conf/default jboss.conf
  Added:       src/etc/conf/default jetty.xml
  Log:
  Configuration files updated for jetty
  
  Revision  Changes    Path
  1.5       +34 -9     jboss/src/etc/conf/default/jboss.conf
  
  Index: jboss.conf
  ===================================================================
  RCS file: /products/cvs/ejboss/jboss/src/etc/conf/default/jboss.conf,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- jboss.conf        2000/11/07 12:15:04     1.4
  +++ jboss.conf        2000/11/10 21:14:21     1.5
  @@ -92,7 +92,9 @@
     -- 
     -- Arguments: #1: where the j2eedeployer should store its config files
     --            #2: the jar deployer: currently only ContainerFactory
  -  --            #3: the war deployer: currently only EmbeddedTomcat
  +  --            #3: the war deployer: you can use tomcat (":service=EmbeddedTomcat")
  +  --                or jetty (":service=Jetty")
  +  --                See below to start these services
     -->
   <MLET CODE = "org.jboss.deployment.J2eeDeployer" ARCHIVE="jboss.jar,../xml.jar" 
CODEBASE="../../lib/ext/">
       <ARG TYPE="java.lang.String" VALUE="../tmp/deploy">
  @@ -102,24 +104,47 @@
   
   
   <!-- 
  -  --  Uncomment this to add Tomcat support.  Be sure to set your 'TOMCAT_HOME' 
  -  -- environment variable before starting JBoss.
  +  -- Uncomment this to add "Stand-alone Stack Tomcat support".  
  +  -- This means that JSP and Servlets will work with EJB in different stacks and 
  +  -- communicate through network invocation.  If you benchmark j2ee please use 
"integrated stack".
  +  -- Also note that you cannot use the J2EE deployer with Tomcat in this 
configuration.
  +  -- Be sure to set your 'TOMCAT_HOME' environment variable before starting JBoss. 
  +  -- Note: this reads the server.xml configuration file of Tomcat, you can't use 
the j2ee deployer
  +  --
     -- MLET CODE = "org.jboss.tomcat.TomcatService" ARCHIVE="jboss.jar" 
CODEBASE="../../lib/ext/">
     -- /MLET>
     -->
   
  +<!-- WARNING: only one of the tomcat services can be configured, either "stand 
alone or integrated" -->
  +
   <!-- 
  -  --  Uncomment this to add Tomcat support. 
  -  -- This service allows you to add and remove Tomcat contexts dynamically
  -  -- through JMX. Note that tomcat's server.xml file will not be processed: 
  -  -- you can only use JMX to add contexts.
  -  -- Be sure to set your 'TOMCAT_HOME' environment variable before starting 
  -  -- JBoss.
  +  -- Uncomment this to add "Integrated Stack (fast) Tomcat support". 
  +  -- This service allows you to integrate the stack of Tomcat and jboss.  
  +  -- Invocations are not going through network but pass native pointers resulting 
in dramatic speed increases.
  +  -- This service allows the J2EE deployer to add and remove Tomcat contexts 
dynamically
  +  -- through JMX for you and in effect deploy EARs. Note that tomcat's server.xml 
file will not be processed: 
  +  -- you can only use JMX to add contexts.  Use the J2EE deployer to deploy full 
EARs on this stack
  +  -- Be sure to set your 'TOMCAT_HOME' environment variable before starting JBoss.
  +  -- 
     -- The ARG tag is the port to run tomcat on.
  +  -- 
     -- MLET CODE = "org.jboss.tomcat.EmbeddedTomcatService" ARCHIVE="jboss.jar" 
CODEBASE="../../lib/ext/">
     -- ARG TYPE="int" VALUE=8080>
     -- /MLET>
     -->
  +
  +<!-- 
  +  -- Uncomment this to add Jetty support. 
  +  -- This service allows you to add and remove Jetty contexts dynamically
  +  -- through JMX.
  +  -- Be sure to set your 'JETTY_HOME' environment variable before starting 
  +  -- JBoss.
  +  -- Replace the ARG tag to give Jetty's XML configuration file.  
  +  -- You can use JBOSS_HOME/conf/default/jetty.xml
  +  --
  +  -- MLET CODE = "org.jboss.jetty.JettyService" ARCHIVE="jetty-service.jar" 
CODEBASE="../../lib/ext/">
  +  -- ARG TYPE="java.lang.String" VALUE="file:/usr/jboss/conf/default/jetty.xml">
  +  -- /MLET>
   
   <MLET CODE = "org.jboss.spydermq.SpyderMQService" ARCHIVE="jboss.jar" 
CODEBASE="../../lib/ext/">
   </MLET>
  
  
  
  1.1                  jboss/src/etc/conf/default/jetty.xml
  
  Index: jetty.xml
  ===================================================================
  <?xml version="1.0"  encoding="ISO-8859-1"?>
  <!DOCTYPE Configure PUBLIC
   "-//Mort Bay Consulting//DTD Configure 1.0//EN"
   "http://jetty.mortbay.com/configure_1_0.dtd">
  
  <!--
  This is a Jetty HTTP server configuration file.  This configuration
  uses the generic com.mortbay.Util.XmlConfiguration class to call
  the normal com.mortbay.HTTP.HttpServer configuration API from
  within an XML script.
  
  The format of this file is described in the configure.dtd file.
  
  The API that can be called by this file is described in the
  Javadoc for Jetty.
  
  The following concepts must be understood when configuring
  a server:
  
  Listener: is a network interface object that
  accepts HTTP requests for the server. SocketListeners accept
  normal requests, while JsseListeners accept SSL requests.
  The threading model of the server is controlled by the
  listener parameters.
  
  WebApplication: is a bundled collection of resources,
  servlets and configuration that can provide a unified
  WWW application.  It is part of the 2.2 servlet standard.
  The contents of the application are configured by the
  web.xml deployment descriptor within the application.
  The configuration of the application within Jetty requires
  on the context of the application to be set.
  
  Context: is a grouping of server resources that share
  the same URL path prefix, class path and resource base.
  A Web application is an example of a specific context.
  Generic contexts may have arbitrary request handlers
  added to them.  All contexts have a path specification
  (frequently the default "/") and an option virtual
  host alias.
  
  Handler:  Handlers are the objects that actually
  service the HTTP requests. Examples of Handlers include
  ServletHandler, ResourceHandler and NotFoundHandler.
  Handlers are contained within Contexts, which provide
  conveniance methods for the common handlers so
  that servlet and file serving may be configured for
  a context without explicit creation of a Handler.
  
  
  This file configures the demo server and is equivalent
  to the com.mortbay.Jetty.Demo class.
  
  $ID: $
  -->
  
  <Configure class="com.mortbay.HTTP.HttpServer">
    <Call name="addListener">
      <Arg>
        <New class="com.mortbay.HTTP.SocketListener">
          <Set name="Port">8080</Set>
          <Set name="MinThreads">5</Set>
          <Set name="MaxThreads">255</Set>
          <Set name="MaxIdleTimeMs">60000</Set>
          <Set name="MaxReadTimeMs">60000</Set>
        </New>
      </Arg>
    </Call>
  
  <!--  Uncomment this to add an SSL listener. 
    <Call name="addListener">
      <Arg>
        <New class="com.mortbay.HTTP.SunJsseListener">
          <Set name="Port">8443</Set>
          <Set name="MinThreads">5</Set>
          <Set name="MaxThreads">255</Set>
          <Set name="MaxIdleTimeMs">50000</Set>
          <Set name="Keystore">etc/demokeystore</Set>
        <Set name="Password">OBF:1vny1zlo1x8e1vnw1vn61x8g1zlu1vn4</Set>
        <Set name="KeyPassword">OBF:1u2u1wml1z7s1z7a1wnl1u2g</Set>
        </New>
      </Arg>
    </Call>
  -->
  
    <Call name="addWebApplication">
      <Arg>/jetty/*</Arg>
      <Arg><SystemProperty name="jetty.home"/>/webapps/jetty.war</Arg>
      <Arg><SystemProperty name="jetty.home"/>/etc/webdefault.xml/</Arg>
    </Call>
  
    <Call name="addContext">
      <Arg>/demo/*</Arg>
      <Set name="ResourceBase"><SystemProperty name="jetty.home"/>/docroot/</Set>
      <Call name="addServlet">
        <Arg>Dump</Arg>
        <Arg>/dump/*,*.DUMP</Arg>
        <Arg>com.mortbay.Servlet.Dump</Arg>
      </Call>
      <Call name="addServlet">
        <Arg>Session</Arg>
        <Arg>/session</Arg>
        <Arg>com.mortbay.Servlet.SessionDump</Arg>
      </Call>
      <Call name="addServlet">
        <Arg>Dispatch</Arg>
        <Arg>/Dispatch/*</Arg>
        <Arg>com.mortbay.Servlet.RequestDispatchTest</Arg>
      </Call>
      <Call name="addServlet">
        <Arg>JSP</Arg>
        <Arg>*.jsp</Arg>
        <Arg>org.apache.jasper.servlet.JspServlet</Arg>
      </Call>
      <Set name="ServingResources">TRUE</Set>
      <Call name="addHandler">
        <Arg><New class="com.mortbay.HTTP.Handler.DumpHandler"/></Arg>
      </Call>
      <Set name="HttpServerAccess">TRUE</Set>
    </Call>
  
    <Call name="addContext">
      <Arg>/servlet/*</Arg>
      <Set name="ClassPath"><SystemProperty name="jetty.home"/>/servlets/</Set>
      <Set name="ServingDynamicServlets">TRUE</Set>
    </Call>
  
    <Call name="addContext">
      <Arg>/javadoc/*</Arg>
      <Set name="ResourceBase"><SystemProperty name="jetty.home"/>/javadoc/</Set>
      <Set name="ServingResources">TRUE</Set>
    </Call>
  
    <Call name="addContext">
      <Arg>/cgi-bin/*</Arg>
      <Set name="ResourceBase"><SystemProperty name="jetty.home"/>/cgi-bin</Set>
      <Call name="addServlet">
        <Arg>Common Gateway Interface</Arg>
        <Arg>/</Arg>
        <Arg>com.mortbay.Servlet.CGI</Arg>
       <Put name="Path">/bin:/usr/bin:/usr/local/bin</Put>
      </Call>
    </Call>
  
    <Call name="addContext">
      <Arg>/</Arg>
      <Call name="addServlet">
        <Arg>Forward</Arg>
        <Arg>/</Arg>
        <Arg>com.mortbay.Servlet.Forward</Arg>
        <Put name="/">/jetty/index.html</Put>
      </Call>
      <Call name="addHandler">
        <Arg><New class="com.mortbay.HTTP.Handler.NotFoundHandler"/></Arg>
      </Call>
    </Call>
  
    <Call name="addRealm">
      <Arg>
        <New class="com.mortbay.HTTP.HashUserRealm">
          <Arg>Jetty Demo Realm</Arg>
          <Arg><SystemProperty name="jetty.home"/>/etc/demoRealm.properties</Arg>
        </New>
      </Arg>
    </Call>
  
    <Set name="LogSink">
      <New class="com.mortbay.Util.RolloverFileLogSink">
        <Set name="LogDir"><SystemProperty name="jetty.home"/>/logs</Set>
        <Set name="RetainDays">90</Set>
        <Set name="MultiDay">false</Set>
        <Set name="Append">true</Set>
      </New>
    </Set>
  
  </Configure>
  
  
  
  
  
  

Reply via email to