Project Dependencies
There are no dependencies for this project. It is a standalone application that does not depend on any other project.
Modified: cocoon/site/site/subprojects/configuration/1.0/dependencies.html URL: http://svn.apache.org/viewvc/cocoon/site/site/subprojects/configuration/1.0/dependencies.html?rev=762445&r1=762444&r2=762445&view=diff ============================================================================== --- cocoon/site/site/subprojects/configuration/1.0/dependencies.html (original) +++ cocoon/site/site/subprojects/configuration/1.0/dependencies.html Mon Apr 6 18:09:51 2009 @@ -1,114 +1,117 @@ - - - - - - - - - - - -
-There are no dependencies for this project. It is a standalone application that does not depend on any other project.
There are no dependencies for this project. It is a standalone application that does not depend on any other project.
Typically the licenses listed for the project are that of the project itself, and not of dependencies.
Apache License Version 2.0, January 2004 @@ -296,24 +296,24 @@ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. -
This document provides an overview of the various documents and links that are part of this project's general information. All of this content is automatically generated by Maven on behalf of the project.
Document | Description |
---|---|
Project License | This is a link to the definitions of project licenses. |
Dependencies | This document lists the projects dependencies and provides information on each dependency. |
Project Team | This document provides information on the members of this project. These are the individuals who have contributed to the project in one form or another. |
Project Summary | This document lists other related information of this project |
This document provides an overview of the various documents and links that are part of this project's general information. All of this content is automatically generated by Maven on behalf of the project.
Document | Description |
---|---|
Project Summary | This document lists other related information of this project |
Dependencies | This document lists the projects dependencies and provides information on each dependency. |
Project Team | This document provides information on the members of this project. These are the individuals who have contributed to the project in one form or another. |
Project License | This is a link to the definitions of project licenses. |
Field | Value |
---|---|
Name | Cocoon Configuration Site |
Description | The Apache Software Foundation provides support for the Apache community of open-source software projects. The Apache projects are characterized by a collaborative, consensus based development process, an open and pragmatic software license, and a desire to create high quality software that leads the way in its field. We consider ourselves not simply a group of projects sharing a server, but rather a community of developers - and users. |
Homepage | http://cocoon.apache.org/subprojects/configuration/1.0/ |
Field | Value |
---|---|
Name | The Apache Software Foundation |
URL | http://www.apache.org/ |
Field | Value |
---|---|
GroupId | org.apache.cocoon |
ArtifactId | cocoon-configuration-site |
Version | 1.0.0-SNAPSHOT |
Type | jar |
Field | Value |
---|---|
Name | The Apache Software Foundation |
URL | http://www.apache.org/ |
Field | Value |
---|---|
GroupId | org.apache.cocoon |
ArtifactId | cocoon-configuration-site |
Version | 1.0.0-SNAPSHOT |
Type | jar |
The Spring Configurator uses Spring's +extensible +XML authoring features and therefore it can be directly used in your Spring +bean configurations. Usually you add the configurator to your global web +application context configuration (which is usually located at +/WEB-INF/applicationContext.xml). The extensible XML authoring requires +that you use the schema based configuration for Spring. Just add the required +namespace definition, a reference to the configurator XML schema to your bean +configuration:
<beans xmlns="http://www.springframework.org/schema/beans" + xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" + xmlns:configurator="http://cocoon.apache.org/schema/configurator" + xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.0.xsd + http://cocoon.apache.org/schema/configurator http://cocoon.apache.org/schema/configurator/cocoon-configurator-1.0.1.xsd"> + ... +</beans> +
Then you can initialize the configurator by adding the settings +element to your bean configuration:
<!-- Activate Cocoon Spring Configurator --> + <configurator:settings/> +
This innocent looking statement initializes the Cocoon Spring Configurator +and provides support for the following features without any additional +configuration:
The Spring Configurator is a useful component providing support in common +configuration issues when using the Spring framework.
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.
When using a framework like Spring there are always the same problems to +solve, like
The Spring Configurator requires
The configurator provides the support of running modes. A running +mode defines the environment the application is currently running in. For +example this can be during development, a test setup or production. As you will +see in just some paragraphs, the configurator can use different configurations +and settings depending on the running mode.
A running mode is just a unique text key, like dev, test +or prod. This key is used to determine the correct configuration at +runtime. Although you can use any text key, it is advisable to use one of the +standard keys (dev, test or prod).
The running mode can be set in two ways: you can either set it in your +applicationContext.xml as a configuration for the settings +element:
<!-- Activate Cocoon Spring Configurator --> + <configurator:settings runningMode="test"/> +
Or you can define the running mode by setting the system property +org.apache.cocoon.mode on startup of your web application, usually you +do this by specifying -Dorg.apache.cocoon.mode=test when starting your +application server. The system property has precedence over the value from the +application context. The default running mode is prod.