A document has been updated:
http://cocoon.zones.apache.org/daisy/documentation/1420.html
Document ID: 1420
Branch: main
Language: default
Name: New in 2.2 (unchanged)
Document Type: Cocoon Document (unchanged)
Updated on: 10/27/07 3:40:05 PM
Updated by: Reinhard Pötz
A new version has been created, state: publish
Parts
=====
Content
-------
This part has been updated.
Mime type: text/xml (unchanged)
File name: (unchanged)
Size: 3762 bytes (previous version: 3701 bytes)
Content diff:
(9 equal lines skipped)
<h1>General</h1>
<ul>
--- <li>Cocoon 2.2 doesn't use an Avalon-based component manager but Spring 2
--- instead.</li>
+++ <li>Cocoon 2.2 doesn't use an Avalon-based component manager any more but
Spring
+++ 2 instead.</li>
<li>Cocoon components (sitemap components as well as general components)
can be
defined as Spring beans now. This brings all the power of Spring (Dependency
Injection, AOP framework, etc.) to the core of Cocoon without having to
rely on
some kind of bridging mechanism. Avalon component configurations are still
supported but deprecated.</li>
<li>Cocoon core has been split up into a bunch of smaller modules (pipeline
api/impl, sitemap api/impl, components, etc.). This is an important step in
--- order to make Cocoon easily embeddable in the future and to define clear
+++ order to make Cocoon more easily embeddable in the future and to define
clear
contracts.</li>
--- <li>Additional validation of sitemaps based on XML schema definitions.</li>
+++ <li>An optional additional validation of sitemaps based on XML schema
+++ definitions.</li>
</ul>
<h1>Modularity</h1>
(59 equal lines skipped)
<h1>Incompatible changes</h1>
--- <p class="fixme">Is there anything? (Logging?)</p>
+++ <p class="fixme">Is there anything? (logging?, custom component
configurations?)
+++ </p>
</body>
</html>
