A document has been updated:
http://cocoon.zones.apache.org/daisy/documentation/1162.html
Document ID: 1162
Branch: main
Language: default
Name: Configuration (unchanged)
Document Type: Cocoon Document (unchanged)
Updated on: 10/3/06 9:49:41 AM
Updated by: Carsten Ziegeler
A new version has been created, state: publish
Parts
=====
Content
-------
This part has been updated.
Mime type: text/xml (unchanged)
File name: (unchanged)
Size: 9466 bytes (previous version: 8995 bytes)
Content diff:
<html>
<body>
+++ <p>The main goal for the new Cocoon 2.2 configuration system is to avoid
+++ patching of any provided configuration file (If you're familiar with
previous
+++ versions of Cocoon you might remember the patching of the cocoon.xconf or
+++ web.xml to satisfy your project needs.)</p>
+++
<h1>Property Configuration</h1>
<p>Cocoon comes with a smart configuration mechanism based on property
files.
(32 equal lines skipped)
<p>You can easily set the running mode by setting the system property
"org.apache.cocoon.mode" on startup of Cocoon, for example:<br/>
--- "-Dorg.apache.cocoon.mode=dev".</p>
+++ "-Dorg.apache.cocoon.mode=dev" or by specifying the mode in your
+++ "applicationContext.xml" (see above). The system property takes precedence
over
+++ the application context configuration.</p>
<p>Currently Cocoon supports three predefined running modes. You can choose
--- between "dev", "test" and "prod".</p>
+++ between "dev", "test" and "prod" or use your own mode.</p>
<h2>Properties and Sitemaps</h2>
(10 equal lines skipped)
"false" at the map:components element in the sitemap.</p>
<p>You can specify your own property directory where all property files are
read
--- from by using the attribute "property-dir" with the directory location at
the
--- map:components element in the sitemap.</p>
+++ from by using the element "map:include-properties" with the attribute "dir"
+++ specifying the directory location inside the map:components element in the
+++ sitemap.</p>
<p>If you don't want that Cocoon tries to replace strings containing a
property
reference in your sitemap, you can set the attribute "replace-properties"
with
the value "false" at the map:components element in the sitemap.</p>
<p>Please note, that you can't use properties to define the values for the
attributes on the map:components element. This means that the possible
values
--- for "use-default-include", "property-dir" and "replace-properties" are
--- hard-coded values which can't be changed using properties.</p>
+++ for "use-default-include" and "replace-properties" are hard-coded values
which
+++ can't be changed using properties.</p>
<h2>Properties and Java Code</h2>
(130 equal lines skipped)
