<?xml version="1.0"?>
<!-- imports user.roles file which defines 
     DBPrism External Cache Invalidator server -->
<cocoon version="2.0" user-roles="/user.roles">
...

	     <!-- DBPrism External invalidate cache Server built-in logicsheet
             defines <cache:registerPage/> xsp tag, to explicity define an
             external controled cached xsp page
	     see ext/xsp/simple_ext.xsp page for example
	     on ext subsitemap
       -->
 <builtin-logicsheet>
   <parameter name="prefix" value="cache"/>
      <parameter name="uri" 
                 value="http://apache.org/cocoon/cache/1.0"/>
      <parameter name="href" 
                 value="resource://org/apache/cocoon/components/language/markup/xsp/java/cache.xsl"/>
 </builtin-logicsheet>

...
  <!-- ESI Invalidation protocol support:
      InMemoryServerImpl parameters:
          initialCapacity        : number      Value for HashMap store
          loadFactor             : number      Value for HashMap store
      DatabaseServerImpl (HSQLDB) parameter:
          jdbcDriver             : JDBC Driver for the repository
          connectString          : JDBC connect string
          username               : database username
          password               : database password
      Common parameters:
          invalidator-user       : user name used for invalidation purpose
          invalidator-pass       : password used for invalidation purpose
          Cleanup-Thread-Interval: number of seconds betwen checking the inv. queue
    -->
    <cache-server class="org.apache.cocoon.components.cache.DatabaseServerImpl"
                  pool-max="1" pool-min="1"
                  logger="core.cache-server">
      <parameter name="jdbcDriver" value="org.hsqldb.jdbcDriver"/>
      <parameter name="connectString" value="jdbc:hsqldb:."/>
      <parameter name="username" value="sa"/>
      <parameter name="password" value=""/>
      <parameter name="invalidator-user" value="invalidator"/>
      <parameter name="invalidator-pass" value="invalidator"/>
      <parameter name="Cleanup-Thread-Interval" value="1"/>
    </cache-server>
...
  <!-- 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">
    <!-- This line is for Tomcat
    	<parameter name="servlet-class" value="org.apache.jasper.servlet.JspServlet"/>
    -->
    <!-- This line is for Oracle OC4J 1.0.x/Orion
    	<parameter name="servlet-class" value="com.evermind.server.http.JSPServlet"/>
    -->
    <!-- This line is for Oracle OC4J 2.0.0.x
    -->
    <parameter name="servlet-class" value=">oracle.jsp.runtimev2.JspServlet"/>
    <parameter name="servlet-name" value="*.jsp"/>
  </jsp-engine>
...
</cocoon>

<?xml version="1.0"?>
<!DOCTYPE role-list [
<!ELEMENT role-list (role+)> 
<!ELEMENT role (hint*)>
<!ELEMENT hint EMPTY>
<!ATTLIST role name CDATA #REQUIRED
               shorthand CDATA #REQUIRED
               default-class CDATA #IMPLIED
>
<!ATTLIST hint shorthand CDATA #REQUIRED
               class CDATA #REQUIRED
>
]>

<role-list>
 <role name="org.apache.cocoon.components.cache.Server"
       shorthand="cache-server"
       default-class="org.apache.cocoon.components.cache.DatabaseServerImpl"/>
</role-list>