cocoon.xconf

Hippo CMS是一个以信息为中心的开源内容管理系统。Hippo CMS目标是供中,大型企业来管理其发布在互连网

      <sitemap>${cms.project-specific.sitemap}</sitemap>
    </values>
  </component-instance>

  <!-- FIXME: couldn't this be moved into an external xml configuration file, and used from an XMLFileModule InputModule? -->
  <component-instance class="org.apache.cocoon.components.modules.input.DefaultsModule" logger="core.modules.input" name="globalconstants">
    <values>
      <locale>nl</locale>
      <cms-fileimportservice-url/>
      <version>v6.05.04</version>
      <cms-preview-url/>
      <cms-history-actions>on</cms-history-actions>
      <cms-use-trash-bin>off</cms-use-trash-bin>
      <thesaurus-path>content/thesaurus/</thesaurus-path>      
      <ldap-user/>      
      <ldap-password/>      
      <ldap-server>localhost</ldap-server>      
      <ldap-searchbase>OU=Users,DC=company,DC=local</ldap-searchbase>
      <extract-shared-text-on-save>off</extract-shared-text-on-save>
      <shared-text-version>off</shared-text-version>
      <cms-use-locking>off</cms-use-locking>
      <cms-use-workflow-on-assets>off</cms-use-workflow-on-assets>
      <cms-references-view>on</cms-references-view>
      <cms-types-dir>context://types</cms-types-dir>
      <cms-types>types.xml</cms-types>
      <aspell-location/>
      <cms-newslettermanager-url/>
    	<cms-newslettermanager-liveserver/>
      <cms-profilemanager-url/>
      <cms-forms-invalidating-pipelines>repository://types</cms-forms-invalidating-pipelines>
      <cms-forms-invalidating-pipelines-seperator>|</cms-forms-invalidating-pipelines-seperator>
      <cms-extensionspath>../hippo-cms-extensions/</cms-extensionspath>
    	<cms-hcamanagerpath>hcamanager</cms-hcamanagerpath>
      <!-- cms-livesite-url is for HCA version 1.01.01 only, deprecated for HCA 1.01.02  -->
      <cms-livesite-url>${cms.livesite.url}</cms-livesite-url>      
      <cms-titlebar-truncate-path-after>-1</cms-titlebar-truncate-path-after>
      <cms-webservice-url/>
      <cms-webservice-object/>
      <cms-webservice-name/>
      <navigation-sortby>caption</navigation-sortby>
      <navigation-sortorder>ascending</navigation-sortorder>
      <mixedsorting>false</mixedsorting>
      <navigation-paging>true</navigation-paging>
      <navigation-pagesize>20</navigation-pagesize>
      <overwrite-uploads>allow</overwrite-uploads>
      <inline-upload-maxsize>80</inline-upload-maxsize>
      <cms-wizard-configuration-xsl/>
      <cms-wizard-configuration-src/>
      <cms-startup-function>start</cms-startup-function>
      <cms-shelf>off</cms-shelf>
    </values>
  </component-instance>

    <component-instance class="org.apache.cocoon.components.modules.input.DateInputModule" logger="core.modules.input" name="date">
      <format>yyyyMMdd</format>
    </component-instance>

</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>

<!-- ========================= Protocol Handlers =========================== -->

  <!-- UH: Declare the source resolver, otherwise the parent sourceresolver is used :-) -->
  <source-resolver/>

  <!--+
      | Source Factories
      |
      | Each source factory adds a special uri schemes to the system.
      +-->
  <source-factories>
    <component-instance class="org.apache.excalibur.source.impl.ResourceSourceFactory" name="resource"/>
    <component-instance class="org.apache.cocoon.components.source.impl.ContextSourceFactory" name="context"/>
    <component-instance class="org.apache.cocoon.components.source.impl.SitemapSourceFactory" logger="core.source.cocoon" name="cocoon"/>
    <!-- The "file:" protocol is modifiable (can be written to) and traversable (directory structures
         can be traversed). -->
    <component-instance class="org.apache.excalibur.source.impl.FileSourceFactory" name="file"/>
    <component-instance class="org.apache.cocoon.components.source.impl.PartSourceFactory" name="upload"/>
    <component-instance class="org.apache.cocoon.components.source.impl.ModuleSourceFactory" name="module"/>
    <component-instance class="nl.hippo.cocoon.source.impl.SiteSourceFactory" name="site"/>
    <component-instance class="nl.hippo.cocoon.source.impl.RepositorySourceFactory" name="repository"/>
    <component-instance class="nl.hippo.cocoon.source.impl.RepositorySourceFactory" name="repository-binary">
        <parameter name="prefix" value="cached-binary:"/>
    </component-instance>
    <component-instance class="nl.hippo.cocoon.source.impl.WebDAVSourceFactory" name="webdav">
      <parameter name="httpstate" value="site:httpstate"/>
    </component-instance>
    <!-- the "*" protocol handles all uri schemes that are not explicitely specified. This includes all
         JDK standard protocols. -->
    <component-instance class="org.apache.excalibur.source.impl.URLSourceFactory" name="*"/>
    
    <!--+
        | Caching source protocol.
        | This protocol extension implements a proxy-like source
        | that can cache the contents of its delegate source.
        | 
        | The uri syntax is as follows:
        | cached:subprotocol:/path[?cocoon:cache-expires=60][&cache-name=main]
        | 
        | Where: 
        | - 'cached' is the caching source protocol scheme name as defined below.
        | - 'subprotcol:/path' identifies the source to get the actual contents from
        |   eg. http://cocoon.apache.org/doco.html?version=1.2
        | - optional querystring parameters that start with 'cocoon:' represent special 
        |   instructions to pass to the implementation.
        |
        | The protocol can be parametrized as follows:
        | - 'async' (false). When this is set to true cached source contents are updated
        |   in the background.
        | - 'cache-role' (org.apache.cocoon.caching.Cache). Use this if you want to use
        |   a Cache other than the default one.
        | - 'refresher-role' (org.apache.cocoon.components.source.impl.Refresher). Use this
        |   if you wish to use a Refresher other than the default one.
        |   A Refresher is used when asynchronic caching is turned on. It is responsible for
        |   updating the cached contents in the background.
        | - 'default-expires' (-1). The expires value if it is not specified on the source
        |    itself.
        +-->
      <component-instance class="nl.hippo.cocoon.components.source.impl.CachingSourceFactory" logger="core.source.caching" name="cached">
        <parameter name="cache-role" value="org.apache.cocoon.caching.Cache/EventAwareRepositoryDoc"/>
      </component-instance>
      <component-instance class="nl.hippo.cocoon.components.source.impl.CachingSourceFactory" logger="core.source.caching" name="cached-binary">
        <parameter name="cache-role" value="org.apache.cocoon.caching.Cache/EventAwareRepositoryBinary"/>
      </component-instance>
  
       
       <component-instance class="nl.hippo.cocoon.source.impl.ExtensionsSourceFactory" name="extensions">
           <cms-extensionspath>../hippo-cms-extensions/</cms-extensionspath>
       </component-instance>
</source-factories>
  
<!-- ================================= 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.