packages: lenya/lenya-cocoon.xconf (NEW) - customized database configuration
pawelz
pawelz at pld-linux.org
Thu Oct 8 13:18:14 CEST 2009
Author: pawelz Date: Thu Oct 8 11:18:14 2009 GMT
Module: packages Tag: HEAD
---- Log message:
- customized database configuration
---- Files affected:
packages/lenya:
lenya-cocoon.xconf (NONE -> 1.1) (NEW)
---- Diffs:
================================================================
Index: packages/lenya/lenya-cocoon.xconf
diff -u /dev/null packages/lenya/lenya-cocoon.xconf:1.1
--- /dev/null Thu Oct 8 13:18:14 2009
+++ packages/lenya/lenya-cocoon.xconf Thu Oct 8 13:18:08 2009
@@ -0,0 +1,3076 @@
+<?xml version="1.0" encoding="UTF-8"?><!--
+ Licensed to the Apache Software Foundation (ASF) under one or more
+ contributor license agreements. See the NOTICE file distributed with
+ this work for additional information regarding copyright ownership.
+ The ASF licenses this file to You under the Apache License, Version 2.0
+ (the "License"); you may not use this file except in compliance with
+ the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
+ -->
+
+<!-- CVS $Id$ -->
+
+<cocoon user-roles="/WEB-INF/classes/org/apache/lenya/lenya.roles" version="2.1">
+
+ <!--+
+ | This is the Apache Cocoon configuration file. This is the place
+ | where you configure the components that Cocoon uses internally (stuff
+ | like the cache) or handles to the pipeline components
+ | (stuff like XML parsers or XSLT processors).
+ +-->
+
+ <!-- Database connection configuration -->
+
+ <datasources>
+
+ <!--
+ - See Excalibur documentation for details
+ - http://excalibur.apache.org/apidocs/org/apache/avalon/excalibur/datasource/ResourceLimitingJdbcDataSource.html
+ -->
+
+ <!-- Use MySQL -->
+
+ <jdbc name="personnel">
+ <pool-controller min="5" max="10"/>
+ <dburl>jdbc:mysql://localhost:3306/cocoondb?autoReconnect=true</dburl>
+ <user>cocoon</user>
+ <password>cocoon</password>
+ </jdbc>
+
+ <jdbc name="LenyaScheduler">
+ <pool-controller min="5" max="10"/>
+ <dburl>jdbc:mysql://localhost:3306/cocoondb?autoReconnect=true</dburl>
+ <user>cocoon</user>
+ <password>cocoon</password>
+ </jdbc>
+
+ <!-- don't forget to enable jdbc driver in web.xml if you use other db engine
+ -
+ - 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.
+ -->
+
+ <!-- HSQLDB example (doesn't work for me)
+ <jdbc logger="core.datasources.personnel" name="personnel">
+ <pool-controller max="10" min="5" timeout="30000"/>
+ <dburl>jdbc:hsqldb:hsql://localhost:9002/cocoondb</dburl>
+ <user>sa</user>
+ <password/>
+ </jdbc>
+
+ <jdbc logger="core.datasources.lenya.scheduler" name="LenyaScheduler">
+ <pool-controller max="10" min="5">
+ <keep-alive>SELECT 1 FROM QRTZ_LOCKS</keep-alive>
+ </pool-controller>
+ <dburl>jdbc:hsqldb:hsql://localhost:9002/cocoondb</dburl>
+ <user>sa</user>
+ <password/>
+ </jdbc>
+ -->
+
+ <!-- you can also use container jdbc connection (doesn't work for me)
+
+ <j2ee name="personnel">
+ <dbname>jdbc/lenya</dbname>
+ </j2ee>
+
+ <j2ee name="LenyaScheduler">
+ <dbname>jdbc/lenya</dbname>
+ </j2ee>
+ -->
+
+ </datasources>
+
+<!-- End of database configuration -->
+
+<!-- =========================== 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.
+ |
+ | Reloading of the sitemap:
+ | The check-reload attribute determines if the sitemap is to be
+ | reloaded on change.
+ | Set to "no", the sitemap is generated once at startup.
+ | Set to "yes", the sitemap is regenerated if it changes.
+ |
+ | For development environment, set the check-reload to yes.
+ | For production environment, it is advisable to set check-reload to no.
+ +-->
+ <sitemap check-reload="yes" file="context://sitemap.xmap" logger="sitemap"/>
+
+<!-- ========================= Sitemap Flowscript ========================== -->
+
+ <!--+
+ | The <flow-interpreters> element is used to describe the flowscript
+ | engines usedd by the current instance.
+ |
+ | The attributes recognized by the <flow-interpreters> element are:
+ |
+ | default (string value):
+ |
+ | the default interpreted language assumed for <map:script>
+ | elements which do not specify a "language" attribute. If not
+ | present, the first language that's described within the
+ | <flow-interpreters> element is assumed to be the default
+ | language.
+ |
+ | Within <flow-interpreters> only <component-instance> elements are
+ | recognized. The attributes recognized by this element are "name"
+ | and "class". "name" specifies the name of a scripting language,
+ | and "class" defines the Java class that implements it. See
+ | org.apache.cocoon.components.flow.Interpreter for the Cocoon
+ | interface with an scripting language interpreter.
+ |
+ | A <component-instance> element contains as subelements the
+ | following elements:
+ |
+ | reload-scripts (boolean value, default false):
+ | whether to check if the scripts source files are modified.
+ | Checking for modification is an expensive operation, so leave
+ | it disabled in a production environment. If not present it is
+ | assumed to be "false". When "true" *all* script files are
+ | checked for modification on each function invocation done using
+ | <map:call function="...">, but not more frequent than the value
+ | of "check-time" (see below).
+ |
+ | check-time (long value, default 1000):
+ | time in miliseconds between the checks for the last modification
+ | date of script files.
+ |
+ | debugger (boolean value, default false):
+ | whether support for the JavaScript debugger should be enabled in
+ | the control flow.
+ +-->
+ <flow-interpreters default="javascript" logger="flow">
+ <!-- FOM (Flow Object Model) -->
+ <component-instance class="org.apache.cocoon.components.flow.javascript.fom.FOM_JavaScriptInterpreter" name="javascript">
+ <load-on-startup>resource://org/apache/cocoon/components/flow/javascript/fom/fom_system.js</load-on-startup>
+ <reload-scripts>${javascript.reload-scripts}</reload-scripts>
+ <check-time>${javascript.check-time}</check-time>
+ <!-- <debugger>enabled</debugger> --> <!-- JavaScript Debugger support -->
+ </component-instance>
+ </flow-interpreters>
+
+ <!--+
+ | Configuration for the continuations manager.
+ |
+ | This section specifies the default time-to-live of continuations
+ | in miliseconds using the "time-to-live" attribute of
+ | the <continuations-manager> element.
+ |
+ | If your site is sharing continuations between sitemaps you
+ | should refactor your application to keep a continuation bound to
+ | a single sitemap. The log will contain warnings which indicate
+ | where a continuation from a different sitemap is used.
+ |
+ | When you cannot do the refactoring in one blow you can turn on
+ | compatibility with shared continuations by setting the
+ | "continuation-sharing-bug-compatible" attribute to "true".
+ |
+ | The <expirations-check> element specifies different policies for
+ | expiring continuations. Currently only the "periodic" type is
+ | supported.
+ |
+ | If you need higher security you can bind your continuations
+ | to session. This way only the session that initially created
+ | the continuation can later resume it. Also if session gets
+ | invalidated all continuations are invalidated as well.
+ | Enable this feature for web applications by setting
+ | 'session-bound-continuations' to true.
+ +-->
+ <continuations-manager continuation-sharing-bug-compatible="false" logger="flow.manager" session-bound-continuations="false" time-to-live="${continuations-manager.time-to-live}">
+ <expirations-check type="periodic">
+ <offset>${continuations-manager.expirations-check.offset}</offset>
+ <period>${continuations-manager.expirations-check.period}</period>
+ </expirations-check>
+ </continuations-manager>
+
+<!-- =================== Sitemap Input/Output Modules ====================== -->
+
+ <!--+
+ | InputModules are a replacement to reading values directly
+ | e.g. from request parameters. By using this abstraction and
+ | indirection, other components can be more generic and changes
+ | to the application logic are easier.
+ |
+ | A number of components already use InputModules: the sitemap processor,
+ | flow, some matchers, the linkrewriting transformer, database actions
+ | and more.
+ |
+ | For example the sitemap processor allows to obtain a value
+ | named "foo" from an the InputModule for request parameters by
+ | writing {request-param:foo} wherever a sitemap variable is
+ | allowed.
+ |
+ | Some InputModules need the help of other InputModules to
+ | obtain values and only apply a function to the obtained value
+ | or change the name of the attribute. These modules usually
+ | carry "Meta" in their name. An example is the ChainMetaModule
+ | which tries several other modules in turn until a non-null
+ | value is obtained or all modules are tied.
+ |
+ | For details and optional configuration parameters refer to the
+ | accompanying javadocs.
+ +-->
+ <input-modules>
+ <component-instance class="org.apache.cocoon.components.modules.input.URLEncodeModule" logger="core.modules.input" name="url-encode">
+ <encoding>UTF-8</encoding>
+ </component-instance>
+ <component-instance class="org.apache.cocoon.components.modules.input.URLDecodeModule" logger="core.modules.input" name="url-decode">
+ <encoding>UTF-8</encoding>
+ </component-instance>
+ <component-instance class="org.apache.cocoon.components.modules.input.GlobalInputModule" logger="core.modules.input" name="global"/>
+ <component-instance class="org.apache.cocoon.components.modules.input.RequestModule" logger="core.modules.input" name="request"/>
+ <component-instance class="org.apache.cocoon.components.modules.input.BaseLinkModule" logger="core.modules.input" name="baselink"/>
+ <component-instance class="org.apache.cocoon.components.modules.input.SessionModule" logger="core.modules.input" name="session"/>
+ <component-instance class="org.apache.cocoon.components.modules.input.RequestParameterModule" logger="core.modules.input" name="request-param"/>
+ <component-instance class="org.apache.cocoon.components.modules.input.RawRequestParameterModule" logger="core.modules.input" name="raw-request-param"/>
+ <component-instance class="org.apache.cocoon.components.modules.input.RequestAttributeModule" logger="core.modules.input" name="request-attr"/>
+ <component-instance class="org.apache.cocoon.components.modules.input.HeaderAttributeModule" logger="core.modules.input" name="request-header"/>
+ <component-instance class="org.apache.cocoon.components.modules.input.SessionAttributeModule" logger="core.modules.input" name="session-attr"/>
+ <component-instance class="org.apache.cocoon.components.modules.input.CookieModule" logger="core.modules.input" name="cookie"/>
+ <component-instance class="org.apache.cocoon.components.modules.input.SystemPropertyModule" logger="core.modules.input" name="system-property"/>
+ <component-instance class="org.apache.cocoon.components.modules.input.StringConstantModule" logger="core.modules.input" name="constant"/>
+ <component-instance class="org.apache.cocoon.components.modules.input.RandomNumberModule" logger="core.modules.input" name="random"/>
+ <component-instance class="org.apache.cocoon.components.modules.input.DigestMetaModule" logger="core.modules.input" name="digest"/>
+ <component-instance class="org.apache.cocoon.components.modules.input.DateInputModule" logger="core.modules.input" name="date">
+ <!-- <format>EEE, d MMM yyyy HH:mm:ss Z</format> -->
+ <!--Eg: Mon, 28 Oct 2002 03:08:49 +1100 -->
+ </component-instance>
+ <component-instance class="org.apache.cocoon.components.modules.input.NullInputModule" logger="core.modules.input" name="nullinput"/>
+ <component-instance class="org.apache.cocoon.components.modules.input.RealPathModule" logger="core.modules.input" name="realpath"/>
+ <component-instance class="org.apache.cocoon.components.modules.input.ContextPathModule" logger="core.modules.input" name="contextpath"/>
+ <component-instance class="org.apache.cocoon.components.modules.input.NamingInputModule" logger="core.modules.input" name="naming">
+ </component-instance>
+ <component-instance class="org.apache.cocoon.components.modules.input.PropertiesFileModule" logger="core.modules.input" name="cocoon-properties">
+ <file src="resource://org/apache/cocoon/cocoon.properties"/>
+ </component-instance>
+ <component-instance class="org.apache.cocoon.components.modules.input.FlowAttributeModule" logger="core.modules.input" name="flow-attribute"/>
+ <component-instance class="org.apache.cocoon.components.modules.input.FlowAttributeModule" logger="core.modules.input" name="flow-attr"/>
+ <component-instance class="org.apache.cocoon.components.modules.input.FlowContinuationModule" logger="core.modules.input" name="flow-continuation"/>
+
+ <component-instance class="org.apache.cocoon.components.modules.input.XMLMetaModule" logger="core.modules.input" name="xmlmeta"/>
+ <component-instance class="org.apache.cocoon.components.modules.input.MapMetaModule" logger="core.modules.input" name="mapmeta"/>
+ <component-instance class="org.apache.cocoon.components.modules.input.DateMetaInputModule" logger="core.modules.input" name="datemeta"/>
+ <component-instance class="org.apache.cocoon.components.modules.input.JXPathMetaModule" logger="core.modules.input" name="jxpath"/>
+ <component-instance class="org.apache.cocoon.components.modules.input.SimpleMappingMetaModule" logger="core.modules.input" name="simplemap"/>
+ <component-instance class="org.apache.cocoon.components.modules.input.LocateResource" logger="core.modules.input" name="locate"/>
+ <component-instance class="org.apache.cocoon.components.modules.input.ChainMetaModule" logger="core.modules.input" name="chain">
+ <input-module name="request-param"/>
+ <input-module name="request-attr"/>
+ <input-module name="session-attr"/>
+ <input-module name="defaults"/>
+ </component-instance>
+
+ <!--+
+ | Following five modules definitions, 'defaults', 'myxml',
+ | 'slashdot' 'random-100-to-500' and 'random-5000-to-10000',
+ | are used only in the samples.
+ +-->
+ <component-instance class="org.apache.cocoon.components.modules.input.DefaultsModule" logger="core.modules.input" name="defaults">
+ <values>
+ <skin>defaultSkin</skin>
+ <base-url>http://localhost:8080/cocoon</base-url>
+ </values>
+ </component-instance>
+ <component-instance class="org.apache.cocoon.components.modules.input.XMLFileModule" logger="core.modules.input" name="myxml">
+ <file src="context://samples/modules/forrestconf.xml"/>
+ </component-instance>
+ <component-instance class="org.apache.cocoon.components.modules.input.XMLFileModule" logger="core.modules.input" name="slashdot">
+ <file src="http://slashdot.org/slashdot.rss"/>
+ </component-instance>
+ <component-instance class="org.apache.cocoon.components.modules.input.XPathXMLFileModule" logger="core.modules.input" name="xmyxml">
+ <file src="context://samples/modules/forrestconf.xml"/>
+ </component-instance>
+ <component-instance class="org.apache.cocoon.components.modules.input.XPathXMLFileModule" logger="core.modules.input" name="varxml">
+ <file src="context://samples/modules/{request-param:dir}/forrestconf.xml"/>
+ </component-instance>
+ <component-instance class="org.apache.cocoon.components.modules.input.RandomNumberModule" logger="core.modules.input" name="random-100-to-500">
+ <min>100</min>
+ <max>500</max>
+ </component-instance>
+ <component-instance class="org.apache.cocoon.components.modules.input.RandomNumberModule" logger="core.modules.input" name="random-5000-to-10000">
+ <min>5000</min>
+ <max>10000</max>
+ </component-instance>
+ <!--..... Start configuration from 'modules' -->
+
+
+ <!-- This input module provides access to the information of a session context -->
+ <component-instance class="org.apache.cocoon.webapps.session.components.ContextInputModule" logger="core.modules.input" name="session-context"/>
+
+<!--..... End configuration from 'modules' -->
+<!--..... Start configuration from 'db-modules-input' -->
+
+
+ <component-instance class="org.apache.cocoon.components.modules.input.CollectionMetaModule" logger="core.modules.input" name="collection"/>
+
+<!--..... End configuration from 'db-modules-input' -->
+<!--..... Start configuration from 'linkrewriter' -->
+
+
+ <!-- For the sitedemo sample -->
+ <component-instance class="org.apache.cocoon.components.modules.input.XMLFileModule" logger="core.modules.xml" name="linkmap">
+ <file src="cocoon://samples/linkrewriter/sitedemo/linkmap"/>
+ <!-- Shouldn't this be the default? -->
+ <reloadable>true</reloadable>
+ </component-instance>
+ <component-instance class="org.apache.cocoon.components.modules.input.SimpleMappingMetaModule" logger="core.modules.mapper" name="site">
+ <input-module name="linkmap"/>
+ <prefix>/site/</prefix>
+ <suffix>/@href</suffix>
+ </component-instance>
+
+ <!-- For the bookdemo sample -->
+ <component-instance class="org.apache.cocoon.components.modules.input.XMLFileModule" logger="core.modules.xml" name="book-raw">
+ <!-- Shouldn't this be the default? -->
+ <file src="cocoon://samples/linkrewriter/bookdemo/linkmap"/>
+ <reloadable>true</reloadable>
+ </component-instance>
+ <component-instance class="org.apache.cocoon.components.modules.input.SimpleMappingMetaModule" logger="core.modules.mapper" name="book">
+ <input-module name="book-raw"/>
+ </component-instance>
+
+<!--..... End configuration from 'linkrewriter' -->
+
+ <component-instance class="org.apache.cocoon.components.modules.input.DateInputModule" logger="core.modules.input" name="date-i18n">
+ <format>yyyy-MM-dd HH:mm:ss Z</format>
+ </component-instance>
+
+ <component-instance class="org.apache.lenya.cms.cocoon.components.modules.input.DateConverterModule" logger="core.modules.input" name="date-iso8601-rfc822">
+ <src-pattern>yyyy-MM-dd HH:mm:ss Z</src-pattern>
+ <pattern>EEE, dd MMM yyyy HH:mm:ss Z</pattern>
+ </component-instance>
+
+ <component-instance class="org.apache.lenya.cms.cocoon.components.modules.input.DocumentInfoModule" logger="sitemap.modules.input.doc-info" name="doc-info"/>
+
+ <component-instance class="org.apache.lenya.cms.cocoon.components.modules.input.DocumentURLModule" logger="core.modules.input.document-url" name="document-url"/>
+
+ <component-instance class="org.apache.lenya.cms.cocoon.components.modules.input.FallbackModule" logger="core.modules.input.fallback" name="fallback">
+ <parameter name="protocol" value="fallback"/>
+ </component-instance>
+
+ <component-instance class="org.apache.cocoon.components.modules.input.ChainMetaModule" logger="core.modules.input" name="forrest">
+ <input-module name="request-param"/>
+ <input-module name="request-attr"/>
+ <input-module name="session-attr"/>
+ <input-module name="defaults"/>
+ <input-module name="page-envelope"/>
+ <input-module name="access-control"/>
+ </component-instance>
+
+ <component-instance class="org.apache.lenya.cms.cocoon.components.modules.input.PageEnvelopeModule" logger="sitemap.modules.input.page-envelope" name="page-envelope"/>
+
+ <component-instance class="org.apache.lenya.cms.cocoon.components.modules.input.ResourceTypeModule" logger="sitemap.modules.input.resource-type" name="resource-type"/>
+
+
+ <component-instance class="org.apache.lenya.cms.cocoon.components.modules.input.LinkingModule" logger="core.modules.input.link" name="link"/>
+
+
+ <component-instance class="org.apache.lenya.cms.cocoon.components.modules.input.ProxyModule" logger="sitemap.modules.input.proxy" name="proxy"/>
+
+ <component-instance class="org.apache.lenya.cms.cocoon.components.modules.input.AccessControlModule" logger="core.modules.input.access-control" name="access-control"/>
+
+
+ <component-instance class="org.apache.lenya.cms.usecase.cocoon.UsecaseModule" logger="core.modules.input.usecase" name="usecase"/>
+
+
+ <component-instance class="org.apache.lenya.inbox.InboxModule" logger="core.modules.input.inbox" name="inbox"/>
+
+ <component-instance class="org.apache.lenya.cms.cocoon.components.modules.input.WorkflowModule" logger="core.modules.input.workflow" name="workflow"/>
+
+
+ <component-instance class="org.apache.lenya.cms.cocoon.components.modules.input.UsecaseDocumentModule" logger="core.modules.input.usecase-document" name="usecase-document"/>
+
+
+ <component-instance class="org.apache.cocoon.components.modules.input.DefaultsModule" name="xopus">
+ <values>
+ <!-- Same as from (local.)build.properties -->
+ <context>Xopus-2.1.79</context>
+ <path>../../../../tomcat-5.5.x/build/build/webapps/ROOT</path>
+ </values>
+ </component-instance>
+
+
+ <component-instance class="org.apache.lenya.cms.cocoon.components.modules.input.SitetreeModule" logger="core.modules.input.sitetree" name="sitetree"/>
+
+
+
+ <component-instance class="org.apache.lenya.modules.lucene.ImageQueryStringModule" logger="core.modules.input.imageQueryString" name="imageQueryString"/>
+
+
+ <component-instance class="org.apache.cocoon.components.modules.input.IndexPathModule" logger="core.modules.input.index-path" name="index-path">
+ </component-instance>
+
+
+ <component-instance class="org.apache.lenya.modules.lucene.QueryStringModule" logger="core.modules.input.queryString" name="queryString"/>
+
+
+ <component-instance class="org.apache.lenya.cms.cocoon.components.modules.input.MetaDataModule" logger="sitemap.modules.input.dublincore" name="dublincore" namespace="http://purl.org/dc/elements/1.1/"/>
+
+ <component-instance class="org.apache.lenya.cms.cocoon.components.modules.input.PropertiesModule" logger="core.modules.input.properties" name="properties"/>
+ </input-modules>
+
+ <!--+
+ | OutputModules are companion modules for InputModules.
+ |
+ | The same principles apply here, only that OutputModules allow
+ | writing data to places. Apparently, there are a lot less
+ | places to write to than to read data from, thus there are only
+ | a few OutputModules coming with Apache Cocoon.
+ |
+ | One special feature of OutputModules is, that they expose some
+ | limited transactional behaviour. Hence it does not suffice to
+ | write a value, but it is required to confirm this at the
+ | end. Until then, the value could not be read from the
+ | corresponding InputModule. This behaviour is not enfored but
+ | it should be expected. Omitting a commit or rollback is an
+ | error.
+ |
+ | OutputModules are currently used by flow, a number of actions
+ | and transformers.
+ +-->
+ <output-modules>
+ <component-instance class="org.apache.cocoon.components.modules.output.RequestAttributeOutputModule" logger="core.modules.output" name="request-attr"/>
+ <component-instance class="org.apache.cocoon.components.modules.output.RequestAttributeMap" logger="core.modules.output" name="request-attr-map"/>
+ <component-instance class="org.apache.cocoon.components.modules.output.SessionAttributeOutputModule" logger="core.modules.output" name="session-attr"/>
+ </output-modules>
+
+<!-- ================================= XML ================================ -->
+
+ <!--+
+ | Entity resolution catalogs
+ |
+ | The default catalog is distributed at WEB-INF/entities/catalog
+ | This is the contextual pathname for Cocoon resources.
+ | You can override this path, if necessary, using the "catalog" parameter:
+ |
+ | <parameter name="catalog" value="WEB-INF/entities/catalog"/>
+ |
+ | However, it is probably desirable to leave this default catalog config
+ | and declare your own local catalogs, which are loaded in addition to
+ | the system catalog.
+ |
+ | There are various ways to do local configuration (see "Entity Catalogs"
+ | documentation). One way is via the CatalogManager.properties file.
+ | As an additional method, you can specify the "local-catalog"
+ | parameter here.
+ |
+ | local-catalog:
+ | The full filesystem pathname to a single local catalog file.
+ |
+ | <parameter name="local-catalog" value="/usr/local/sgml/mycatalog"/>
+ |
+ | verbosity:
+ | The level of messages for status/debug (messages go to standard output)
+ | The following messages are provided ...
+ | 0 = none
+ | 1 = ? (... not sure yet)
+ | 2 = 1+, Loading catalog, Resolved public, Resolved system
+ | 3 = 2+, Catalog does not exist, resolvePublic, resolveSystem
+ | 10 = 3+, List all catalog entries when loading a catalog
+ | (Cocoon also logs the "Resolved public" messages.)
+ |
+ | <parameter name="verbosity" value="2"/>
+ +-->
+ <entity-resolver logger="core.resolver">
+ <parameter name="catalog" value="WEB-INF/entities/catalog"/>
+ <parameter name="verbosity" value="1"/>
+ </entity-resolver>
+
+ <!--+
+ | XML Parser
+ |
+ | Apache Cocoon requires a JAXP 1.1 parser. The default parser is
+ | org.apache.excalibur.xml.impl.JaxpParser.
+ | Note: 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.excalibur.xml.impl.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.excalibur.xml.sax.SAXParser=org.apache.excalibur.xml.impl.XercesParser
+ |
+ | Configuration parameters for the JaxpParser (not the XercesParser!):
+ | - validate (boolean, default = false): should the parser validate
+ | parsed documents?
+ | Note: 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) do not like
+ | to be reused after failure.
+ | - sax-parser-factory (string, optional) : 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, optional) : the name of the
+ | DocumentBuilderFactory implementation to be used (similar to
+ | sax-parser-factory for DOM).
+ | - drop-dtd-comments : should comment() events from DTD's be dropped?
+ | Note: Since this implementation does not support the DeclHandler
+ | interface anyway, it is quite useless to only have the comments
+ | from DTD. And the comment events from the internal DTD subset
+ | would appear in the serialized output again.
+ +-->
+ <xml-parser class="org.apache.excalibur.xml.impl.JaxpParser" logger="core.xml-parser" pool-max="${xml-parser.pool-max}">
+ <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="drop-dtd-comments" value="true"/>
+ </xml-parser>
+
+ <!--+
+ | XSLT Processor
+ |
+ | 'incremental-processing' (only works with Xalan) allows the XSLT
+ | processor to start the output of the transformation as soon as possible.
+ | if set to false, the transforer waits until the end of the
+ | transformation to deliver the output.
+ | WARNING: * if you enable incremental-processing, you should be aware of
+ | the following bug:
+ | http://issues.apache.org/bugzilla/show_bug.cgi?id=13186
+ | * incremental-processing creates an additional, non-pooled thread.
+ | * using incremental-processing does not save memory, the input
+ | tree will still be build completely.
+ | * incremental processing is a 'static' thing in Xalan: if you
+ | enable it on one xslt-processor, enable it on all.
+ +-->
+ <xslt-processor logger="core.xslt">
+ <parameter name="use-store" value="true"/>
+ <parameter name="incremental-processing" value="false"/>
+ </xslt-processor>
+
+ <!--+
+ | XSLT Processor using xsltc from Xalan
+ | For Interpreted Xalan use:
+ | <transformer-factory>org.apache.xalan.processor.TransformerFactoryImpl</transformer-factory>
+ +-->
+ <component class="org.apache.cocoon.components.xslt.TraxProcessor" logger="core.xslt" role="org.apache.excalibur.xml.xslt.XSLTProcessor/xsltc">
+ <parameter name="use-store" value="true"/>
+ <parameter name="transformer-factory" value="org.apache.xalan.xsltc.trax.TransformerFactoryImpl"/>
+ </component>
+
+ <!--+
+ | Xalan XSLT Processor
+ +-->
+ <component class="org.apache.cocoon.components.xslt.TraxProcessor" logger="core.xslt" role="org.apache.excalibur.xml.xslt.XSLTProcessor/xalan">
+ <parameter name="use-store" value="true"/>
+ <parameter name="incremental-processing" value="false"/>
<<Diff was trimmed, longer than 597 lines>>
More information about the pld-cvs-commit
mailing list