Apache Cocoon

Apache Cocoon implements some of the same principles that made Spring such a success in the first place, allowing developers to work with complex code structures in an organized manner.

As it's with Spring, Apache Cocoon heavily utilizes components to separate functionality, allowing developers only to load what they need, keeping and application's size down as much as possible.

Components can talk to the core and amongst themselves using the notion of "pipelines".

Because Cocoon is also implemented as a Java servlet and as a Java CLI tool, it can work with any other J2EE application without disruptions.

As with any other Apache project, Cocoon is very well documented by its community.

What is new in this release:

• Changes:
• XSLTTransformer and SchemaProcessorTransformer created resources have been cached.
• The o.a.c.controller.SpringControllerComponent became a CachingPipelineComponent. For that purpose the controller invocation was separated into a setup and an execution phase. If the controller provides a cache key after the setup, this is returned by the SpringControllerComponent and the pipeline that embeds the controllers becomes cacheable.
• Upgrade to cocoon-jnet-1.2.0.
• Upgrade all modules that have a dependency on Spring version 3.0.5.RELEASE.

Requirements:

• Java 1.4.2 or above