cocoon-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject cvs commit: xml-cocoon2/src/scratchpad/schecoon/webapp/WEB-INF cocoon.xconf
Date Thu, 21 Mar 2002 23:32:07 GMT
ovidiu      02/03/21 15:32:07

  Added:       src/scratchpad/schecoon/webapp/WEB-INF cocoon.xconf
  Moved from webapp/ here.
  Revision  Changes    Path
  1.1                  xml-cocoon2/src/scratchpad/schecoon/webapp/WEB-INF/cocoon.xconf
  Index: cocoon.xconf
  <?xml version="1.0"?>
  <cocoon version="2.0" user-roles="/user.roles">
  <!-- ================ Apache Cocoon configuration file ================== -->
  <!-- For full description of the components and their parameters ...
       - Apache Cocoon User Documentation at /userdocs/
       - webapp/cocoon.xconf (this file) - describes each core component
       - each optional component/.../*.xconf - these describe the parameters
       for each component and are automatically included at build-time.
       The notes that accompany the settings below are intended to be concise.
  <!-- ===================== General Components =========================== -->
    <!-- Parser:
      The default parser used in Apache Cocoon is
      org.apache.avalon.excalibur.xml.JaxpParser. Apache Cocoon requires a 
      JAXP 1.1 parser.
      If you have problems because your servlet environment uses its own
      parser not conforming to JAXP 1.1 try using the alternative
      XercesParser instead of the JaxpParser. To activate the XercesParser,
      change the class attribute to
      You will also need to add a system property to your JVM,
      probably on the startup of your servlet engine like this:
      Configuration for the JaxpParser (not the XercesParser!):
      - validate (boolean, default = false): This parameter causes the parser 
          to be a validating parser.
          XML validation is only being used for the documentation build.
          (If you are going to use it elsewhere, then do so with caution.)
          You really should have validated all of your XML documents already,
          according to their proper DTD or schema. Do not expect Cocoon to do it.
      - namespace-prefixes (boolean, default = false) : do we want
          namespaces declarations also as 'xmlns:' attributes ?
          Note : setting this to true confuses some XSL processors (e.g. Saxon).
      - stop-on-warning (boolean, default = true) : should the parser
          stop parsing if a warning occurs ?
      - stop-on-recoverable-error (boolean, default = true) : should the parser
          stop parsing if a recoverable error occurs ?
      - reuse-parsers (boolean, default = true) : do we want to reuse
          parsers or create a new parser for each parse ?
          Note : even if this parameter is true, parsers are not
          recycled in case of parsing errors : some parsers (e.g. Xerces) don't like
          to be reused after failure.
      - sax-parser-factory (string) : the name of the SAXParserFactory
          implementation class to be used instead of using the standard JAXP mechanism
          (SAXParserFactory.newInstance()). This allows to choose
          unambiguously the JAXP implementation to be used when several of them are
          available in the classpath.
      - document-builder-factory (string) : the name of the
          DocumentBuilderFactory implementation to be used (similar to
          sax-parser-factory for DOM).
    <xml-parser class="org.apache.avalon.excalibur.xml.JaxpParser"
      <parameter name="validate" value="false"/>
      <parameter name="namespace-prefixes" value="false"/>
      <parameter name="stop-on-warning" value="true"/>
      <parameter name="stop-on-recoverable-error" value="true"/>
      <parameter name="reuse-parsers" value="false"/>
      <parameter name="sax-parser-factory" value="???"/>
      <parameter name="document-builder-factory" value="???"/>
    <!-- ============================ STORE ============================ -->
    <!-- Persistent store for the cache. Two store implementations to choose
           * FilesystemStore: Simple. Dependable. Thorougly tested.
           * JispFilesystemStore: Scalable. New kid on the block.
         Common configuration parameters:
           use-cache-directory: Indicates that cache directory specified in
                                web.xml should be used.
           use-work-directory: Indicates that work directory specified in
                               web.xml should be used.
           directory: Specifies directory to use. Absolute or relative to the
                      work directory.
    <cache-persistent class=""
      <parameter name="use-cache-directory" value="true"/>
    <!-- Memory Storing: -->
    <cache-transient class=""
       <!-- Indicates how many objects will be hold in the cache.
       When the number of maxobjects has been reached. The last object in the 
       cache will be thrown out. -->
       <parameter name="maxobjects" value="100"/>
       <!-- Turns the swapping of the objects into persistent cache on
            and off. -->
       <parameter name="use-persistent-cache" value="true"/>
    <!-- Store Janitor:
      Be careful with the heapsize and freememory parameters. Wrong values can
      cause high cpu usage. Example configuration:
      Jvm settings: 
        -Xms100000000 -Xmx200000000
      store-janitor settings:
         <parameter name="freememory" value="5000000"/>
         <parameter name="heapsize" value="150000000"/>
      Heapsize *must* be higher then the -Xms parameter and *must* be lower or
      equal than -Xmx. It is recommended to have heapsize equal to -Xmx, especially
      on Sun's JVM which are unable to shrink its heap once it grows above minimum. 
      Freememory parameter *must* be lower than -Xms, and should be greater than
      amount of memory necessary for normal application operation.
    <store-janitor class=""
       <!-- How much free memory shall be available in the jvm -->                 
       <parameter name="freememory" value="1000000"/>
       <!-- Indicates the limit of the jvm memory consumption. The default max 
       heapsize for Sun's JVM is 64Mb -->
       <parameter name="heapsize" value="67108864"/>
       <!-- How often shall the cleanup thread check memory -->
       <parameter name="cleanupthreadinterval" value="10"/>
       <!-- Indicates the thread priority of the cleanup thread -->
       <parameter name="threadpriority" value="5"/>
       <!-- How much percent of the elements of each registered Store shall
       be removed when low on memory. Default 10% -->
       <parameter name="percent_to_free" value="10"/>
    <!-- ============================ STORE END ========================= -->
    <!-- XSLT Processor:
      For Xalan: Turn 'incremental-processing' to true if you want a continous output (if
set to false the transformer 
      delivers SAX events after all transformations has been done). -->
    <xslt-processor class="org.apache.cocoon.components.xslt.XSLTProcessorImpl"
       <parameter name="use-store" value="true"/>
       <parameter name="incremental-processing" value="true"/>
    <!-- Xpath Processor:
    <xpath-processor class="org.apache.cocoon.components.xpath.XPathProcessorImpl"
    <!-- URL Factory:
      The url factory adds special url protocols to the system, they are then
      available inside Cocoon, e.g. as a source argument for one of the sitemap
    <url-factory logger="core.url-factory">
      <!-- Allows access to resources available from the ClassLoader,
           using getResource() method. -->
      <protocol name="resource" class="org.apache.cocoon.components.url.ResourceURLFactory"/>
      <!-- Allows access to resources available from the servlet context,
           using getResource() method. -->
      <protocol name="context"  class="org.apache.cocoon.components.url.ContextURLFactory"/>
      <!-- Add here protocol factories for your own protocols -->
    <!-- Program Generator:
      The ProgamGenerator builds programs from a XML document written in a
         root-package: persistent code repository.
    <program-generator logger="core.program-generator">
      <parameter name="auto-reload" value="true"/>
      <parameter name="root-package" value="org.apache.cocoon.www"/>
      <parameter name="preload" value="true"/>
    <!-- JSP Engine:
      The JspGenerator selects a JSPEngine component. The JSPEngine component
      launches a JSP servlet engine of your servlet container, feeds the
      HttpRequest into the JSP servlet engine, and pipes the jsp response as
      SAX events into Cocoon2. The JSP page is specified by the HttpRequest.
      This way you can continue to use your JSP pages. Your migration from JSP
      to XSP may be done step by step. You may specify your JSP pages either as
      JSP scriptlets or as JSP-XML. But keep in mind that your JSP output should
      be valid XML.
    <jsp-engine logger="core.jsp-engine">
      <parameter name="servlet-class" value="org.apache.jasper.servlet.JspServlet"/>
      <parameter name="servlet-name" value="*.jsp"/>
    <!-- Xscript:
    <xscript logger="core.xscript">
      <parameter name="xscript:copy-of" value="resource://org/apache/cocoon/components/xscript/xslt/copy-of.xsl"/>
      <parameter name="xscript:value-of" value="resource://org/apache/cocoon/components/xscript/xslt/value-of.xsl"/>
    <!-- Programming Languages: -->
      <java-language name="java" logger="">
        <!-- Compiler parameter specifies which class to use to compile Java.
             Possible variants are:
               Javac. Requires javac.jar (included with Cocoon distribution).
               Pizza. Requires pizza.jar (included with Cocoon distribution).
               Jikes. Requires IBM jikes compiler to be present in the PATH  -->
        <parameter name="compiler" value=""/>
        <!-- Specifies which formatter to use to format source code.
             This parameter is optional. 
             It is commented out because of bug #5689: Java "code-formatter" incorrectly formats
double values
        <parameter name="code-formatter" value=""/>
        <!-- A singleton-like implementation of a ClassLoader -->
        <parameter name="class-loader" value="org.apache.cocoon.components.classloader.ClassLoaderManagerImpl"/>
      <!-- Interpreted JavaScript language -->
      <js-language name="js" logger="core.language.js"/>
    <!-- Class loader:
      A singleton-like implementation of a ClassLoader.
    <classloader class="org.apache.cocoon.components.classloader.ClassLoaderManagerImpl"
    <!-- Markup Languages:
      This section defines several builtin logicsheets. A logicsheet is an XML
      filter used to translate user-defined, dynamic markup into equivalent
      code embedding directives for a given markup language.
      <xsp-language name="xsp" logger="core.markup.xsp">
        <parameter name="prefix" value="xsp"/>
        <parameter name="uri" value=""/>
        <!-- Defines the XSP Core logicsheet for the Java language -->
        <target-language name="java">
          <parameter name="core-logicsheet" value="resource://org/apache/cocoon/components/language/markup/xsp/java/xsp.xsl"/>
          <!-- The Request logicsheet (taglib) is an XSP logicsheet that wraps XML tags

               around standard request operations -->
            <parameter name="prefix" value="xsp-request"/>
            <parameter name="uri" value=""/>
            <parameter name="href" value="resource://org/apache/cocoon/components/language/markup/xsp/java/request.xsl"/>
          <!-- The Response logicsheet (taglib) is an XSP logicsheet that wraps XML tags

               around standard response operations -->
            <parameter name="prefix" value="xsp-response"/>
            <parameter name="uri" value=""/>
            <parameter name="href" value="resource://org/apache/cocoon/components/language/markup/xsp/java/response.xsl"/>
          <!-- The Session logicsheet (taglib) is an XSP logicsheet that wraps XML tags
               standard session operations. Specifically, the Session logicsheet provides
               XML interface to most methods of the HttpSession object (see the Java Servlet
               Specification, version 2.2 ) for more information. -->
            <parameter name="prefix" value="xsp-session"/>
            <parameter name="uri" value=""/>
            <parameter name="href" value="resource://org/apache/cocoon/components/language/markup/xsp/java/session.xsl"/>
          <!-- The Cookie logicsheet (taglib) is an XSP logicsheet that wraps XML tags

               around standard cookie operations -->
            <parameter name="prefix" value="xsp-cookie"/>
            <parameter name="uri" value=""/>
            <parameter name="href" value="resource://org/apache/cocoon/components/language/markup/xsp/java/cookie.xsl"/>
          <!-- The ESQL logicsheet is an XSP logicsheet that performs sql queries and 
               serializes their results as XML. This allows you to work with data from a 
               wide variety of different sources when using Apache Cocoon. -->
            <parameter name="prefix" value="esql"/>
            <parameter name="uri" value=""/>
            <parameter name="href" value="resource://org/apache/cocoon/components/language/markup/xsp/java/esql.xsl"/>
            <parameter name="prefix" value="log"/>
            <parameter name="uri" value=""/>
            <parameter name="href" value="resource://org/apache/cocoon/components/language/markup/xsp/java/log.xsl"/>
            <parameter name="prefix" value="util"/>
            <parameter name="uri" value=""/>
            <parameter name="href" value="resource://org/apache/cocoon/components/language/markup/xsp/java/util.xsl"/>
          <!-- The xsp-formval taglib serves as interface to retrieve validation results

               from a request attribute -->
            <parameter name="prefix" value="xsp-formval"/>
            <parameter name="uri" value=""/>
            <parameter name="href" value="resource://org/apache/cocoon/components/language/markup/xsp/java/form-validator.xsl"/>
          <!-- The sel taglib allows to put multiple pages / view into
               one xsp. While in general it is good style to put
               different views into different xsp because they're more
               easily maintained, this is a useful feature with
               e.g. with long forms that are broken into parts -->
            <parameter name="prefix" value="sel"/>
            <parameter name="uri" value=""/>
            <parameter name="href" value="resource://org/apache/cocoon/components/language/markup/xsp/java/sel.xsl"/>
            <parameter name="prefix" value="action"/>
            <parameter name="uri" value=""/>
            <parameter name="href" value="resource://org/apache/cocoon/components/language/markup/xsp/java/action.xsl"/>
          <!-- The capture taglib is for capturing parts of the XSP-generated XML as
               XML fragments or DOM nodes -->
            <parameter name="prefix" value="capture"/>
            <parameter name="uri" value=""/>
            <parameter name="href" value="resource://org/apache/cocoon/components/language/markup/xsp/java/capture.xsl"/>
            <parameter name="prefix" value="xscript"/>
            <parameter name="uri" value=""/>
            <parameter name="href" value="resource://org/apache/cocoon/components/language/markup/xsp/java/xscript.xsl"/>
            <parameter name="prefix" value="soap"/>
            <parameter name="uri" value=""/>
            <parameter name="href" value="resource://org/apache/cocoon/components/language/markup/xsp/java/soap.xsl"/>
            <parameter name="prefix" value="jpath"/>
            <parameter name="uri" value=""/>
            <parameter name="href" value="resource://org/apache/cocoon/markup/xsp/jpath.xsl"/>
        <target-language name="js">
          <parameter name="core-logicsheet" value="resource://org/apache/cocoon/components/language/markup/xsp/javascript/xsp.xsl"/>
            <parameter name="prefix" value="xsp-request"/>
            <parameter name="uri" value=""/>
            <parameter name="href" value="resource://org/apache/cocoon/components/language/markup/xsp/javascript/request.xsl"/>
            <parameter name="prefix" value="xsp-response"/>
            <parameter name="uri" value=""/>
            <parameter name="href" value="resource://org/apache/cocoon/components/language/markup/xsp/javascript/response.xsl"/>
            <parameter name="prefix" value="xsp-session"/>
            <parameter name="uri" value=""/>
            <parameter name="href" value="resource://org/apache/cocoon/components/language/markup/xsp/javascript/session.xsl"/>
      <!-- Defines Sitemap Core logicsheet for the Java language -->
      <sitemap-language name="sitemap" logger="core.markup.sitemap">
        <parameter name="prefix" value="map"/>
        <parameter name="uri" value=""/>
        <target-language name="java">
          <parameter name="core-logicsheet" value="resource://org/apache/cocoon/components/language/markup/sitemap/java/sitemap.xsl"/>
    <!-- Datasources:
      <jdbc name="personnel" logger="core.datasources.personnel">
            If you have an Oracle database, and are using the the
        pool-controller below, you should add the attribute
        "oradb" and set it to true.
        <pool-controller min="5" max="10" oradb="true"/>
        That way the test to see if the server has disconnected
        the JdbcConnection will function properly.
        <pool-controller min="5" max="10"/>
            If you need to ensure an autocommit is set to true or
        false, then create the "auto-commit" element below.
        The default is true.
    <!-- Stream Pipeline:
      Either collects a Reader and lets it produce a character stream
      or connects an EventPipeline with a Serializer and lets them produce
      the character stream. Alternatives to CachingStreamPipeline are:
      <stream-pipeline class="org.apache.cocoon.components.pipeline.NonCachingStreamPipeline"/>
    <stream-pipeline class="org.apache.cocoon.components.pipeline.CachingStreamPipeline"
                     pool-max="32" pool-min="8" pool-grow="4"/>
    <!-- Event Pipeline:
      Connects the generator and the various transformers and produces a
      character stream. Alternatives to CachingEventPipeline are:
      <event-pipeline class="org.apache.cocoon.components.pipeline.NonCachingEventPipeline"/>
      <event-pipeline class="org.apache.cocoon.components.profiler.ProfilingCachingEventPipeline"/>
      <event-pipeline class="org.apache.cocoon.components.profiler.ProfilingNonCachingEventPipeline"/>
    <event-pipeline class="org.apache.cocoon.components.pipeline.CachingEventPipeline"
                    pool-max="32" pool-min="8" pool-grow="4"/>
    <!-- Compiling xml to byte streams.
      The xml-serializer "compiles" xml sax events into a byte stream
      and the xml-deserializer does the same vice versa.
      Make sure, that if you change one of these components, that you
      may have to change the other one as well, as they might have
      a dependency.
    <xml-serializer class="org.apache.cocoon.components.sax.XMLByteStreamCompiler"
    <xml-deserializer class="org.apache.cocoon.components.sax.XMLByteStreamInterpreter"
    <!-- SAXConnector:
      Connects the various pipeline components.
      LoggingSAXConnector logs SAX events between pipeline components
      into cocoon's log file.
      ProfilingSAXConnector gathers timing information.
      Uncomment one of the following lines for using the SAXConnector.
    <sax-connector class="org.apache.cocoon.components.saxconnector.LoggingSAXConnector"/>
    <sax-connector class="org.apache.cocoon.components.profiler.ProfilingSAXConnector"/>
    <!-- Profiler:
      The profiler facilitates the gathering of statistics about timings of
      different steps of pipelines. Profiler consists of several components:
       profiling pipeline, profiling SAX connector, and profiler generator
      which are used to generate the profile report. You need to enable all of
      these components to use profiler.
      Uncomment the following line to use profiler.
    <!-- Resource Monitor:
      The Monitor keeps track on changes to a Resource.
    <monitor logger="core.monitor">
      <thread priority="5" frequency="10000"/>
  <!-- ======================== The sitemap  ============================== -->
    <!-- Reloading of the sitemap:
      The check-reload attribute determines if the sitemap is reloaded on change.
      Set to "no", the sitemap is generated once at startup.
      Set to "yes", the sitemap is regenerated if it changes.
      The reload-method specifies the method for the regeneration:
      asynchron: If the sitemap changes, the sitemap is regenerated at the
                 next request in the background and the incoming request is
                 served with the old sitemap. All subsequent requests are
                 served with the old sitemap until the regeneration in the
                 background has finished.
      synchron: If the sitemap changes, the sitemap is regenerated at the
                next request. When the regeneration is finished, the request
                (and all subsequent ones) is served with the new sitemap.
      For development environment, set the reload-method to synchron and the
      check-reload to yes.
      For production environment, it is advisable to set the reload-method to
      asynchron and for more safety the check-reload to no.
    <!--sitemap class="org.apache.cocoon.treeprocessor.TreeProcessor" file="sitemap.xmap"
reload-method="asynchron" check-reload="yes" logger="sitemap"/-->
      New implementation of the sitemap. It is interpreted, so load times are super-fast,
      and request processing is slightly faster than with the compiled engine thanks to
      the HotSpot VM.
      To use this engine, comment the declaration above and uncomment the declaration below.
    <sitemap class="org.apache.cocoon.components.treeprocessor.TreeProcessor"
  <!-- ===================== Sitemap Components =========================== -->
    <!-- Here defined some core Cocoon sitemap components, as File generator
         or XSLT transformer. Note that syntax of this file slightly differs
         from the syntax of <map:components> section of the sitemap.xmap file.
      <component-instance name="file" class="org.apache.cocoon.generation.FileGenerator"
                          pool-max="32" pool-min="8" pool-grow="4"/>
      <component-instance name="serverpages" class="org.apache.cocoon.generation.ServerPagesGenerator"
                          pool-max="32" pool-min="4" pool-grow="2"/>
      <component-instance name="directory" class="org.apache.cocoon.generation.DirectoryGenerator"
                          pool-max="16" pool-min="2" pool-grow="2"/>
      <component-instance name="request" class="org.apache.cocoon.generation.RequestGenerator"
                          pool-max="16" pool-min="2" pool-grow="2"/>
      <component-instance name="status" class="org.apache.cocoon.generation.StatusGenerator"
                          pool-max="16" pool-min="2" pool-grow="2"/>
      <component-instance name="xslt" class="org.apache.cocoon.transformation.TraxTransformer"
                          pool-max="32" pool-min="8" pool-grow="2">
      <component-instance name="log" class="org.apache.cocoon.transformation.LogTransformer"
                          pool-max="16" pool-min="2" pool-grow="2"/>
      <component-instance name="xinclude" class="org.apache.cocoon.transformation.XIncludeTransformer"
                          pool-max="16" pool-min="2" pool-grow="2"/>
      <component-instance name="cinclude" class="org.apache.cocoon.transformation.CIncludeTransformer"
                          pool-max="16" pool-min="2" pool-grow="2"/>
      <component-instance name="links" class="org.apache.cocoon.serialization.LinkSerializer"
      <component-instance name="xml" class="org.apache.cocoon.serialization.XMLSerializer"
      <component-instance name="html" class="org.apache.cocoon.serialization.HTMLSerializer"
                          pool-max="32" pool-min="4" pool-grow="4">
      <component-instance name="resource" class="org.apache.cocoon.reading.ResourceReader"
      <component-instance name="wildcard" class="org.apache.cocoon.matching.WildcardURIMatcher"
      <component-instance name="regexp" class="org.apache.cocoon.matching.RegexpURIMatcher"
      <component-instance name="add-employee" class="org.apache.cocoon.acting.DatabaseAddAction"
      <component-instance name="del-employee" class="org.apache.cocoon.acting.DatabaseDeleteAction"
      <component-instance name="upd-employee" class="org.apache.cocoon.acting.DatabaseUpdateAction"

In case of troubles, e-mail:
To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message