cocoon.xconf

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

<?xml version="1.0" encoding="UTF-8"?>
<cocoon user-roles="/WEB-INF/user.roles" version="2.1">

<!-- =========================== 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" config="resource://org/apache/cocoon/components/treeprocessor/treeprocessor-builtins.xml" 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>true</reload-scripts>
      <check-time>4000</check-time>
      <!--  <debugger>enabled</debugger> -->  <!-- JavaScript Debugger support -->
    </component-instance>
  </flow-interpreters>
  
  <forms-cachemanager/>  
  

  
  <editor-flow-helper/>
  

  
  <!--+
    | 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="true" time-to-live="18000000">
    <expirations-check type="periodic">
      <offset>180000</offset>
      <period>180000</period>
    </expirations-check>
  </continuations-manager>
  


  <!--+
      | 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.
      |
      | The <expirations-check> element specifies different policies for
      | expiring continuations. Currently only the "periodic" type is
      | supported.
      +-->
  

<!-- =================== 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.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.SessionAttributeModule" logger="core.modules.input" name="session-attr"/>
    <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.RandomNumberModule" logger="core.modules.input" name="random"/>
    <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.RealPathModule" logger="core.modules.input" name="realpath"/> 
    <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-attr"/>
    <component-instance class="org.apache.cocoon.components.modules.input.FlowContinuationModule" logger="core.modules.input" name="flow-continuation"/>

    <!--+
      | This JXPath based input module provides access to the current 
      | SiteConfiguration object.
      | SiteConfigurations are resolved using the domain of the current request.
      | Which configurations belong to which domains is specified in sites.xconf.
      | This is the place where the SiteConfiguration objects are configured.
      + -->
    <component-instance class="nl.hippo.cocoon.modules.SiteConfigurationInputModule" logger="core.modules.site" name="site"/>

    <!--+
      | This JXPath based input module provides access to the current 
      | RepositoryConfiguration object.
      | RepositoryConfigurations are resolved using the domain of the current request.
      | Which configurations belong to which domains is specified in sites.xconf.
      | This is the place where the RepositoryConfiguration objects are configured.
      + -->
    <component-instance class="nl.hippo.cocoon.modules.RepositoryConfigurationInputModule" logger="core.modules.repository" name="repository"/>

     <!--+
      | This requestUri based input module, enable to return the initial part 
      | of a requestUri. For example,
      | {requesturi:2} returns "foo/bar" when the requestUri would be /foo/bar/foo2/bar2
      + -->
    <component-instance class="nl.hippo.cocoon.components.modules.input.RequestUriModule" logger="core.modules.site" name="requesturi"/>

  
  
  <component-instance class="nl.hippo.forrest.locationmap.LocationMapModule" logger="core.modules.linkmap" name="lm">
    <file src="context://locationmap.xml"/>
    <eventCacheable>false</eventCacheable>
  </component-instance>


  <!--+
    | This input module reads the property values of the currently active object.
    | The currently active object is identified by {request-param:objectUri}, 
    | prefixed by the {repository:root} value of the currently active request.
    | 
    | SourceProperties are scoped relative to a namespace. Therefore this
    | module provides a way to declare namespaces and their prefixes. A default
    | namespace can be specified to avoid having to use a prefix for that namespace.
    | If no namespace is explicitly configured the first namespace declaration 
    | is implicitly taken as the default.
    + -->
  <component-instance class="nl.hippo.cocoon.modules.SourcePropertiesInputModule" logger="core.modules.object" name="object">
    <src>repository:/{request-param:objectUri}</src>
    <namespace prefix="D" uri="DAV:"/>
    <namespace default="true" prefix="H" uri="http://hippo.nl/cms/1.0"/>
  </component-instance>

  <component-instance class="nl.hippo.cocoon.components.modules.input.EventAwareXMLFileModule" logger="core.modules.model" name="model">
    <cacheable>true</cacheable>
    <reloadable>true</reloadable>
    <file src="cocoon://types.xml"/>
  </component-instance>
  
  <component-instance class="nl.hippo.cocoon.components.modules.input.EventAwareXMLFileModule" logger="core.modules.wizard-includes" name="wizard-includes">
    <cacheable>true</cacheable>
    <reloadable>true</reloadable>
    <file src="cocoon://wizard/includes"/>
  </component-instance>

  <component-instance class="org.apache.cocoon.components.modules.input.DefaultsModule" logger="core.modules.input" name="projectconstants">
    <values>