You are viewing a plain text version of this content. The canonical link for it is here.
Posted to svn@forrest.apache.org by th...@apache.org on 2006/06/25 18:15:03 UTC
svn commit: r417027 - in /forrest/trunk:
main/webapp/WEB-INF/xconf/forrest-core.xconf site-author/status.xml
Author: thorsten
Date: Sun Jun 25 09:15:02 2006
New Revision: 417027
URL: http://svn.apache.org/viewvc?rev=417027&view=rev
Log:
Activating flow in forrest by defining the related components in our core.xconf. Thanks to David that found out that we did not declare the flow components.
Modified:
forrest/trunk/main/webapp/WEB-INF/xconf/forrest-core.xconf
forrest/trunk/site-author/status.xml
Modified: forrest/trunk/main/webapp/WEB-INF/xconf/forrest-core.xconf
URL: http://svn.apache.org/viewvc/forrest/trunk/main/webapp/WEB-INF/xconf/forrest-core.xconf?rev=417027&r1=417026&r2=417027&view=diff
==============================================================================
--- forrest/trunk/main/webapp/WEB-INF/xconf/forrest-core.xconf (original)
+++ forrest/trunk/main/webapp/WEB-INF/xconf/forrest-core.xconf Sun Jun 25 09:15:02 2006
@@ -78,7 +78,89 @@
+-->
<sitemap check-reload="yes" file="context://sitemap.xmap" logger="sitemap"/>
<!-- config="resource://org/apache/cocoon/components/treeprocessor/treeprocessor-builtins.xml" -->
-
+ <!-- ========================= 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" (if no property is overriding this). 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).
+ | The default for this function is determined by the value of the
+ | reloading property 'org.apache.cocoon.reloading.flow'.
+ |
+ | 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 exported="false" name="javascript" class="org.apache.cocoon.components.flow.javascript.fom.FOM_JavaScriptInterpreter">
+ <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>
+
+ <!--+
+ | 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.
+ |
+ | 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 logger="flow.manager" time-to-live="3600000"
+ session-bound-continuations="false">
+ <expirations-check type="periodic">
+ <offset>180000</offset>
+ <period>180000</period>
+ </expirations-check>
+ </continuations-manager>
<!-- =================== Sitemap Input/Output Modules ====================== -->
Modified: forrest/trunk/site-author/status.xml
URL: http://svn.apache.org/viewvc/forrest/trunk/site-author/status.xml?rev=417027&r1=417026&r2=417027&view=diff
==============================================================================
--- forrest/trunk/site-author/status.xml (original)
+++ forrest/trunk/site-author/status.xml Sun Jun 25 09:15:02 2006
@@ -141,7 +141,9 @@
</action>
<!-- 2006-07 -->
-
+ <action context="code" type="update" dev="TS" due-to="David Crossley"> Updated the
+ forrest-core.xconf and declared the core components that are needed
+ for flow. This makes it possible to use flow in forrest.</action>
<!-- 2006-06 -->
<action context="code" type="update" dev="BD">