You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@cocoon.apache.org by ni...@apache.org on 2002/03/18 20:23:51 UTC
cvs commit: xml-cocoon2/src/webapp/WEB-INF cocoon.xconf web.xml
nicolaken 02/03/18 11:23:51
Modified: src/webapp/search sitemap.xmap
src/webapp/WEB-INF web.xml
Added: src/webapp/WEB-INF cocoon.xconf
Log:
Partial commit of new samples structure.
Samples go in samples/ dir with theit own sitemap.
All scratchpad samples that are in the samples/ subdir are copied in webapp samples automatically by installscratchpadwar target.
cocoon.xconf is moved in WEB-INF for security reasons.
Added new "gump" target to build; it calls docs, javadocs, test and package.
Revision Changes Path
1.3 +7 -103 xml-cocoon2/src/webapp/search/sitemap.xmap
Index: sitemap.xmap
===================================================================
RCS file: /home/cvs/xml-cocoon2/src/webapp/search/sitemap.xmap,v
retrieving revision 1.2
retrieving revision 1.3
diff -u -r1.2 -r1.3
--- sitemap.xmap 25 Jan 2002 04:04:50 -0000 1.2
+++ sitemap.xmap 18 Mar 2002 19:23:51 -0000 1.3
@@ -45,16 +45,6 @@
-->
<map:generators default="file">
- <map:generator name="file"
- src="org.apache.cocoon.generation.FileGenerator"
- label="content"
- pool-max="32" pool-min="16" pool-grow="4"/>
- <map:generator name="serverpages"
- src="org.apache.cocoon.generation.ServerPagesGenerator"
- label="content"/>
- <map:generator name="html"
- src="org.apache.cocoon.generation.HTMLGenerator"
- label="content"/>
<map:generator name="search"
src="org.apache.cocoon.generation.SearchGenerator"
label="content"/>
@@ -71,12 +61,6 @@
-->
<map:transformers default="xslt">
- <map:transformer name="xslt"
- src="org.apache.cocoon.transformation.TraxTransformer"
- pool-max="32" pool-min="16" pool-grow="4">
- <use-request-parameters>false</use-request-parameters>
- <use-browser-capabilities-db>false</use-browser-capabilities-db>
- </map:transformer>
<map:transformer name="log"
src="org.apache.cocoon.transformation.LogTransformer"/>
</map:transformers>
@@ -90,26 +74,14 @@
reader. They are useful for delivering binary content like images.
-->
-<map:readers default="resource">
- <map:reader name="resource" src="org.apache.cocoon.reading.ResourceReader"/>
-</map:readers>
+<map:readers default="resource"/>
<!--
Serializers consume SAX events and produce a character stream. Every
pipeline needs to be terminated by a serializer.
-->
-<map:serializers default="html">
- <map:serializer name="links"
- src="org.apache.cocoon.serialization.LinkSerializer"/>
- <map:serializer name="xml"
- mime-type="text/xml"
- src="org.apache.cocoon.serialization.XMLSerializer"
- pool-max="32" pool-min="16" pool-grow="4"/>
- <map:serializer name="html"
- mime-type="text/html"
- src="org.apache.cocoon.serialization.HTMLSerializer"/>
-</map:serializers>
+<map:serializers default="html"/>
<!--
@@ -125,20 +97,7 @@
during pipeline setup.
-->
- <map:matchers default="wildcard">
- <map:matcher name="wildcard" src="org.apache.cocoon.matching.WildcardURIMatcher"/>
- <map:matcher name="regexp" src="org.apache.cocoon.matching.RegexpURIMatcher"/>
- <map:matcher name="request" src="org.apache.cocoon.matching.RequestParamMatcher"/>
- <map:matcher name="sessionstate" src="org.apache.cocoon.matching.WildcardSessionAttributeMatcher">
- <attribute-name>org.apache.cocoon.SessionState</attribute-name>
- </map:matcher>
- <map:matcher name="next-page" src="org.apache.cocoon.matching.WildcardParameterValueMatcher">
- <parameter-name>next-state</parameter-name>
- </map:matcher>
- <map:matcher name="referer-match" src="org.apache.cocoon.matching.WildcardHeaderMatcher">
- <header-name>referer</header-name>
- </map:matcher>
- </map:matchers>
+ <map:matchers default="wildcard"/>
<!--
@@ -151,29 +110,7 @@
during pipeline setup.
-->
-<map:selectors default="browser">
- <map:selector name="browser" src="org.apache.cocoon.selection.BrowserSelector">
- <!-- # NOTE: The appearance indicates the search order. This is very important since
- # some words may be found in more than one browser description. (MSIE is
- # presented as "Mozilla/4.0 (Compatible; MSIE 4.01; ...")
- -->
- <browser name="explorer" useragent="MSIE"/>
- <browser name="pocketexplorer" useragent="MSPIE"/>
- <browser name="handweb" useragent="HandHTTP"/>
- <browser name="avantgo" useragent="AvantGo"/>
- <browser name="imode" useragent="DoCoMo"/>
- <browser name="opera" useragent="Opera"/>
- <browser name="lynx" useragent="Lynx"/>
- <browser name="java" useragent="Java"/>
- <browser name="wap" useragent="Nokia"/>
- <browser name="wap" useragent="UP"/>
- <browser name="wap" useragent="Wapalizer"/>
- <browser name="mozilla5" useragent="Mozilla/5"/>
- <browser name="mozilla5" useragent="Netscape6/"/>
- <browser name="netscape" useragent="Mozilla"/>
- </map:selector>
- <map:selector name="parameter" src="org.apache.cocoon.selection.ParameterSelector"/>
- </map:selectors>
+<map:selectors default="browser"/>
<!--
Actions are executed during pipeline setup. Their purpose is to
@@ -216,23 +153,6 @@
</map:views>
-<!-- =========================== Resources ================================= -->
-
-<!--
- Resources are pipeline fragments that may be used from different
- pipeline fragments. For our needs, they behave exactly like
- pipelines, only that they are not accessible from outside.
- Hence I will explain what's inside below for pipelines.
--->
-
-
-<!-- ========================== Action sets ================================ -->
-
-<!--
- Action sets group actions together. If some actions are often used
- together in pipeline fragments, it's easier to group them and refer
- to the group. For more info, please see the docs.
--->
<!-- =========================== Pipelines ================================= -->
@@ -265,15 +185,6 @@
<map:pipelines>
- <!-- Utility for viewing source xml or html-->
- <map:pipeline>
- <map:match pattern="**.source">
- <map:generate src="{1}" />
- <map:transform src="context://stylesheets/simple-xml2html.xsl"/>
- <map:serialize/>
- </map:match>
- </map:pipeline>
-
<!-- sub-sitemap example pipeline -->
<map:pipeline>
<map:match pattern="images/*.gif">
@@ -297,20 +208,13 @@
javadocs:
"[...] All <map:parameter> declarations will be made
available in the XSLT stylesheet as xsl:variables. [...]"
- -->
- <map:transform src="context://stylesheets/dynamic-page2html.xsl">
+ --><!--
+ <map:transform src="stylesheets/dynamic-page2html.xsl">
<map:parameter name="view-source" value="search/{1}-index.xsp"/>
- </map:transform>
+ </map:transform>-->
<map:serialize/>
</map:match>
- <map:handle-errors>
- <!--
- This pipeline specifies a different error handler.
- -->
- <map:transform src="context://stylesheets/system/error2html.xsl"/>
- <map:serialize status-code="500"/>
- </map:handle-errors>
</map:pipeline>
</map:pipelines>
1.8 +1 -1 xml-cocoon2/src/webapp/WEB-INF/web.xml
Index: web.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/src/webapp/WEB-INF/web.xml,v
retrieving revision 1.7
retrieving revision 1.8
diff -u -r1.7 -r1.8
--- web.xml 4 Mar 2002 15:59:48 -0000 1.7
+++ web.xml 18 Mar 2002 19:23:51 -0000 1.8
@@ -34,7 +34,7 @@
-->
<init-param>
<param-name>configurations</param-name>
- <param-value>/cocoon.xconf</param-value>
+ <param-value>/WEB-INF/cocoon.xconf</param-value>
</init-param>
<!--
1.1 xml-cocoon2/src/webapp/WEB-INF/cocoon.xconf
Index: cocoon.xconf
===================================================================
<?xml version="1.0"?>
<cocoon version="2.0">
<!-- ================ 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
class="org.apache.avalon.excalibur.xml.XercesParser"
You will also need to add a system property to your JVM,
probably on the startup of your servlet engine like this:
-Dorg.apache.avalon.excalibur.xml.Parser=org.apache.avalon.excalibur.xml.XercesParser
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"
logger="core.xml-parser">
<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="???"/>
-->
</xml-parser>
<!-- ============================ STORE ============================ -->
<!-- Persistent store for the cache. Two store implementations to choose
from:
* 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="org.apache.cocoon.components.store.FilesystemStore"
logger="core.store.persistent">
<parameter name="use-cache-directory" value="true"/>
</cache-persistent>
<!-- Memory Storing: -->
<cache-transient class="org.apache.cocoon.components.store.MRUMemoryStore"
logger="core.store.transient">
<!-- 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"/>
</cache-transient>
<!-- Store Janitor:
Be careful with the heapsize and freememory parameters. Wrong values can
cause high cpu usage. Example configuration:
Jvm settings:
-Xmx200000000
store-janitor settings:
<parameter name="freememory" value="5000000"/>
<parameter name="heapsize" value="150000000"/>
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 should be greater than amount of memory necessary for normal
application operation.
-->
<store-janitor class="org.apache.cocoon.components.store.StoreJanitorImpl"
logger="core.store.janitor">
<!-- 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-janitor>
<!-- ============================ 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"
logger="core.xslt-processor">
<parameter name="use-store" value="true"/>
<parameter name="incremental-processing" value="true"/>
</xslt-processor>
<!-- Xpath Processor:
-->
<xpath-processor class="org.apache.avalon.excalibur.xml.xpath.XPathProcessorImpl"
logger="core.xpath-processor"/>
<!-- 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
components.
-->
<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 -->
</url-factory>
<!-- Source Handler:
The source handler adds special url protocols to the system, they are
then available inside Cocoon, e.g. as a source argument for one of the
sitemap components.
-->
<source-handler logger="core.source-handler">
<!-- file protocol : this is a WriteableSource -->
<protocol name="file" class="org.apache.cocoon.components.source.FileSourceFactory"/>
</source-handler>
<!-- Program Generator:
The ProgamGenerator builds programs from a XML document written in a
MarkupLanguage.
auto-reload:
root-package: persistent code repository.
preload:
-->
<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"/>
</program-generator>
<!-- 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"/>
</jsp-engine>
<!-- 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"/>
</xscript>
<!-- Programming Languages: -->
<programming-languages>
<java-language name="java" logger="core.language.java">
<!-- 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="org.apache.cocoon.components.language.programming.java.JstyleFormatter"/>
-->
<!-- A singleton-like implementation of a ClassLoader -->
<parameter name="class-loader" value="org.apache.cocoon.components.classloader.ClassLoaderManagerImpl"/>
</java-language>
</programming-languages>
<!-- Class loader:
A singleton-like implementation of a ClassLoader.
-->
<classloader class="org.apache.cocoon.components.classloader.ClassLoaderManagerImpl"
logger="core.classloader"/>
<!-- 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.
-->
<markup-languages>
<xsp-language name="xsp" logger="core.markup.xsp">
<parameter name="prefix" value="xsp"/>
<parameter name="uri" value="http://apache.org/xsp"/>
<target-language name="java">
<!-- Defines the XSP Core logicsheet for the Java language -->
<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 -->
<builtin-logicsheet>
<parameter name="prefix" value="xsp-request"/>
<parameter name="uri" value="http://apache.org/xsp/request/2.0"/>
<parameter name="href" value="resource://org/apache/cocoon/components/language/markup/xsp/java/request.xsl"/>
</builtin-logicsheet>
<!-- The Response logicsheet (taglib) is an XSP logicsheet that wraps XML tags
around standard response operations -->
<builtin-logicsheet>
<parameter name="prefix" value="xsp-response"/>
<parameter name="uri" value="http://apache.org/xsp/response/2.0"/>
<parameter name="href" value="resource://org/apache/cocoon/components/language/markup/xsp/java/response.xsl"/>
</builtin-logicsheet>
<!-- The Session logicsheet (taglib) is an XSP logicsheet that wraps XML tags around
standard session operations. Specifically, the Session logicsheet provides an
XML interface to most methods of the HttpSession object (see the Java Servlet API
Specification, version 2.2 ) for more information. -->
<builtin-logicsheet>
<parameter name="prefix" value="xsp-session"/>
<parameter name="uri" value="http://apache.org/xsp/session/2.0"/>
<parameter name="href" value="resource://org/apache/cocoon/components/language/markup/xsp/java/session.xsl"/>
</builtin-logicsheet>
<!-- The Cookie logicsheet (taglib) is an XSP logicsheet that wraps XML tags
around standard cookie operations -->
<builtin-logicsheet>
<parameter name="prefix" value="xsp-cookie"/>
<parameter name="uri" value="http://apache.org/xsp/cookie/2.0"/>
<parameter name="href" value="resource://org/apache/cocoon/components/language/markup/xsp/java/cookie.xsl"/>
</builtin-logicsheet>
<!-- 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. -->
<builtin-logicsheet>
<parameter name="prefix" value="esql"/>
<parameter name="uri" value="http://apache.org/cocoon/SQL/v2"/>
<parameter name="href" value="resource://org/apache/cocoon/components/language/markup/xsp/java/esql.xsl"/>
</builtin-logicsheet>
<builtin-logicsheet>
<parameter name="prefix" value="log"/>
<parameter name="uri" value="http://apache.org/xsp/log/2.0"/>
<parameter name="href" value="resource://org/apache/cocoon/components/language/markup/xsp/java/log.xsl"/>
</builtin-logicsheet>
<builtin-logicsheet>
<parameter name="prefix" value="util"/>
<parameter name="uri" value="http://apache.org/xsp/util/2.0"/>
<parameter name="href" value="resource://org/apache/cocoon/components/language/markup/xsp/java/util.xsl"/>
</builtin-logicsheet>
<!-- The xsp-formval taglib serves as interface to retrieve validation results
from a request attribute -->
<builtin-logicsheet>
<parameter name="prefix" value="xsp-formval"/>
<parameter name="uri" value="http://apache.org/xsp/form-validator/2.0"/>
<parameter name="href" value="resource://org/apache/cocoon/components/language/markup/xsp/java/form-validator.xsl"/>
</builtin-logicsheet>
<!-- 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 -->
<builtin-logicsheet>
<parameter name="prefix" value="sel"/>
<parameter name="uri" value="http://apache.org/xsp/sel/1.0"/>
<parameter name="href" value="resource://org/apache/cocoon/components/language/markup/xsp/java/sel.xsl"/>
</builtin-logicsheet>
<builtin-logicsheet>
<parameter name="prefix" value="action"/>
<parameter name="uri" value="http://apache.org/cocoon/action/1.0"/>
<parameter name="href" value="resource://org/apache/cocoon/components/language/markup/xsp/java/action.xsl"/>
</builtin-logicsheet>
<!-- The capture taglib is for capturing parts of the XSP-generated XML as
XML fragments or DOM nodes -->
<builtin-logicsheet>
<parameter name="prefix" value="capture"/>
<parameter name="uri" value="http://apache.org/cocoon/capture/1.0"/>
<parameter name="href" value="resource://org/apache/cocoon/components/language/markup/xsp/java/capture.xsl"/>
</builtin-logicsheet>
<builtin-logicsheet>
<parameter name="prefix" value="xscript"/>
<parameter name="uri" value="http://apache.org/xsp/xscript/1.0"/>
<parameter name="href" value="resource://org/apache/cocoon/components/language/markup/xsp/java/xscript.xsl"/>
</builtin-logicsheet>
<builtin-logicsheet>
<parameter name="prefix" value="soap"/>
<parameter name="uri" value="http://apache.org/xsp/soap/3.0"/>
<parameter name="href" value="resource://org/apache/cocoon/components/language/markup/xsp/java/soap.xsl"/>
</builtin-logicsheet>
</target-language>
</xsp-language>
<!-- 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="http://apache.org/cocoon/sitemap/1.0"/>
<target-language name="java">
<parameter name="core-logicsheet" value="resource://org/apache/cocoon/components/language/markup/sitemap/java/sitemap.xsl"/>
</target-language>
</sitemap-language>
</markup-languages>
<!-- Datasources: -->
<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.
<auto-commit>false</auto-commit>
The default is true.
-->
<dburl>@database-url@</dburl>
<user>@database-user@</user>
<password>@database-password@</password>
</jdbc>
</datasources>
<!-- 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"
logger="core.stream-pipeline"
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"
logger="core.event-pipeline"
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"
logger="core.xml-serializer"/>
<xml-deserializer class="org.apache.cocoon.components.sax.XMLByteStreamInterpreter"
logger="core.xml-deserializer"/>
<!-- 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.
<profiler/>
-->
<!-- Resource Monitor:
The Monitor keeps track on changes to a Resource.
-->
<monitor logger="core.monitor">
<thread priority="5" frequency="10000"/>
</monitor>
<!-- ======================== 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 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" logger="sitemap"/-->
</cocoon>
----------------------------------------------------------------------
In case of troubles, e-mail: webmaster@xml.apache.org
To unsubscribe, e-mail: cocoon-cvs-unsubscribe@xml.apache.org
For additional commands, e-mail: cocoon-cvs-help@xml.apache.org