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: Overview
Date Wed, 15 Nov 2006 20:51:46 GMT
A document has been updated:

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

Document ID: 1258
Branch: main
Language: default
Name: Overview (unchanged)
Document Type: Cocoon Document (unchanged)
Updated on: 11/15/06 8:51:39 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: 4076 bytes (previous version: 3117 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>
+++ 
    <p>Cocoon is a framework consisting of many different components. All these
    components are managed by a component container. Starting with Cocoon 2.2 this
    container is the <a href="http://www.springframework.org">Spring framework</a>.
(21 equal lines skipped)
    <p>This context listener is invoked by the servlet container on startup of your
    web application. By default the configuration for the application context is
    read from the file "WEB-INF/applicationContext.xml". This is the place to
--- configure the Cocoon components:</p>
+++ configure the Cocoon components. Cocoon uses the namespace authoring features of
+++ Spring 2.0:</p>
    
    <pre>&lt;beans xmlns="http://www.springframework.org/schema/beans""
           xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
(13 equal lines skipped)
           add a bean conforming to the Avalon Logger interface to this definition
           and leave out the loggingConfiguration attribute.
       --&gt;
---   &lt;avalon:avalon location="/WEB-INF/cocoon/cocoon.xconf"
---                  loggingConfiguration="/WEB-INF/cocoon/log4j.xconf"/&gt;
+++   &lt;avalon:avalon loggingConfiguration="/WEB-INF/cocoon/log4j.xconf"/&gt;
    
+++ 
+++   &lt;!-- Add your own spring beans here or in separate configuration files --&gt;
+++ 
    &lt;/beans&gt;
    </pre>
    
--- <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>
+++ <p>The two elements shown above are required to get Cocoon up and running inside
+++ your web application. The first one, "cocoon:settings", initializes the Cocoon
+++ properties mechanism and the Cocoon Spring configuration support. The second
+++ element, "avalon:avalon", sets up the Spring-Avalon-Bridge. This bridge allows
+++ you to run Avalon-based components in a Spring container; these Avalon
+++ components are configured using the well-known Avalon-configuration files. And
+++ that's it. These two innocent looking statements do a lot of work behind the
+++ scenes and add all necessary beans to the Spring application context. Once the
+++ application context is up and running, Cocoon is ready as well. You can either
+++ use the provided servlets to map requests to Cocoon or you can integrate Cocoon
+++ into your web application framework by getting the Cocoon beans from the Spring
+++ application context.</p>
    
    </body>
    </html>


Mime
View raw message