cocoon-docs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [DAISY] Updated: Introduction to the Spring Configurator
Date Thu, 11 Jan 2007 08:41:21 GMT
A document has been updated:

Document ID: 1304
Branch: main
Language: default
Name: Introduction to the Spring Configurator (unchanged)
Document Type: Cocoon Document (unchanged)
Updated on: 1/11/07 8:41:09 AM
Updated by: Carsten Ziegeler

A new version has been created, state: publish


This part has been updated.
Mime type: text/xml (unchanged)
File name:  (unchanged)
Size: 1828 bytes (previous version: 78 bytes)
Content diff:
--- <p>This is the Cocoon Spring Configurator!</p>
+++ <h1>The Cocoon Spring Configurator</h1>
+++ <p>The Spring Configurator is a useful component providing support in common
+++ configuration issues when using the Spring framework. Although this product has
+++ been developed inside the Cocoon project, it is aimed at making easier the usage
+++ of Spring in each and every web application; it is not tied to the famous Cocoon
+++ web application framework and can be used standalone. The impact on your code is
+++ nearly zero and the Spring Configurator as only Spring itself as a dependency.
+++ </p>
+++ <h2>Motivation</h2>
+++ <p>When using a framework like Spring there are always the same problems to
+++ solve, like</p>
+++ <ul>
+++ <li>Where do I store my bean configurations?</li>
+++ <li>How can I parameterize them dynamically?</li>
+++ <li>Where do I store these extra information?</li>
+++ <li>How can I handle different environments like a testing environment, a
+++ development environment and a production environment?</li>
+++ <li>How can I distribute not only code but also corresponding configurations?
+++ </li>
+++ <li>How can I distribute partial web applications?</li>
+++ <li>How do I manage hierarchial web application contexts?</li>
+++ </ul>
+++ <p>Of course Spring is flexible enough to enable solutions to the above
+++ problems, but you have to do it and implement it for your solution. And there is
+++ more than one way of doing this and each and every project ends up developing
+++ its own "proprietary" solution. A best practice and a standardized way of doing
+++ these things would be great. And guess what, the Spring Configurator is the
+++ answer to your problems. Like Maven has standardized the build process, the
+++ Spring Configurator standardizes the way of dealing with various configuration
+++ issues with Spring. Ok, enough motivation, let's see what the Spring
+++ configurator can provide for your work.</p>

View raw message