You are viewing a plain text version of this content. The canonical link for it is here.
Posted to docs@cocoon.apache.org by da...@cocoon.zones.apache.org on 2008/10/01 10:53:19 UTC
[DAISY] Updated: Introduction to the Spring Configurator

A document has been updated:

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

Document ID: 1304
Branch: main
Language: default
Name: Introduction to the Spring Configurator (previously Introduction)
Document Type: Cocoon Document (unchanged)
Updated on: 10/1/08 8:53:02 AM
Updated by: David Legg

A new version has been created, state: draft

Parts
=====

Content
-------
This part has been updated.
Mime type: text/xml (unchanged)
File name:  (unchanged)
Size: 1511 bytes (previous version: 1787 bytes)
Content diff:
    <html>
    <body>
    
    <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>
+++ configuration issues when using the Spring framework.</p>
    
+++ <p>Although the code was developed as part of Cocoon, it is aimed at making it
+++ easier to use Spring in any web application.  It has no dependencies on Cocoon
+++ and can be used standalone. The impact on your code is nearly zero and the
+++ Spring Configurator has only Spring itself as a dependency.</p>
+++ 
    <h2>Motivation</h2>
    
    <p>When using a framework like Spring there are always the same problems to
(2 equal lines skipped)
    <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>Where do I store this extra information?</li>
+++ <li>How can I handle different environments for testing or development or
+++ production?</li>
+++ <li>How can I distribute code configuration information?</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>
+++ <p>Of course Spring is flexible enough to handle these problems, but you have to
+++ implement your own solution.  The danger here is that every project ends up
+++ developing its own "proprietary" solution.</p>
    
+++ <p>A standardized way of doing these things would be great.  Guess what!, the
+++ Spring Configurator is the answer to your problems. Just like Maven has
+++ standardized the build process, the Spring Configurator standardizes the way of
+++ dealing with various configuration issues with Spring.</p>
+++ 
    </body>
    </html>