cocoon-docs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From da...@cocoon.zones.apache.org
Subject [DAISY] Updated: Property Configuration
Date Wed, 15 Nov 2006 21:01:26 GMT
A document has been updated:

http://cocoon.zones.apache.org/daisy/documentation/1261.html

Document ID: 1261
Branch: main
Language: default
Name: Property Configuration (unchanged)
Document Type: Cocoon Document (unchanged)
Updated on: 11/15/06 9:01:21 PM
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: 6568 bytes (previous version: 6018 bytes)
Content diff:
(4 equal lines skipped)
    The configuration of Cocoon (or more precisely of the components) is based on
    XML files for the various components. To customize these configuration files
    without changing the files itself you can define properties to which you can
--- refer to from within the configuration files (and sitemaps).</p>
+++ refer to from within the configuration files (and sitemaps and your own code).
+++ In addition, Cocoon provides integrated support for the Spring property override
+++ mechanism, which is described in more detail <a href="daisy:1259">here</a>.</p>
    
    <p>You can define as many property files and define your own properties as you
    want. Store them in the "WEB-INF/cocoon/properties" directory and Cocoon will
    read all of them on startup in alphabetical order. If two files provide values
    for the same property, the last definition wins. Please note that any changes
    you make to the property files will not be reflected during runtime. The changes
    will take effect, the next time you startup the Cocoon web application (or
--- restart the servlet context).</p>
+++ restart the servlet context). For block specific properties have a look here
+++ (FIND CORRECT LINK).</p>
    
    <p>You can refer to the values of a property by using the common
    ${PROPERTY_NAME} syntax in your configuration file or sitemap (this includes
(2 equal lines skipped)
    <h1>Running modes</h1>
    
    <p>Cocoon extends the property based configuration mechanism by "running
--- modes". You define a running mode when you start Cocoon (default is "prod"). The
--- name of the running mode is used to read additional property files on startup.
--- Cocoon reads first all property files from "WEB-INF/cocoon/properties" and after
--- that from "WEB-INF/cocoon/properties/${RUNNING_MODE}".</p>
+++ modes". You have two possibilities to define the running mode: the running mode
+++ can either be set by using a system property or in the application context
+++ configuration. The system property has precedence over the value from the
+++ application context. The default running mode is "prod". The name of the running
+++ mode is used to read additional property files and configuration files on
+++ startup. Cocoon reads first all property files from "WEB-INF/cocoon/properties"
+++ and after that from "WEB-INF/cocoon/properties/${RUNNING_MODE}".</p>
    
    <p>For example if you have different database connections during development and
    in production, just put a properties file containing the connection information
(9 equal lines skipped)
    "applicationContext.xml" (see above). The system property takes precedence over
    the application context configuration.</p>
    
+++ <p>TODO: Document setting the running mode in applicationContext.xml</p>
+++ 
    <p>Currently Cocoon supports three predefined running modes. You can choose
    between "dev", "test" and "prod" or use your own mode.</p>
    
(78 equal lines skipped)


Mime
View raw message