A document has been updated:
http://cocoon.zones.apache.org/daisy/documentation/1285.html
Document ID: 1285
Branch: main
Language: default
Name: Welcome (unchanged)
Document Type: WebpageWithSidebar (unchanged)
Updated on: 12/29/06 7:30:41 PM
Updated by: Reinhard Pötz
A new version has been created, state: publish
Parts
=====
Sidebar
-------
This part has been updated.
Mime type: text/xml (unchanged)
File name: (unchanged)
Size: 1848 bytes (previous version: 1570 bytes)
Content diff:
(22 equal lines skipped)
<h1>What are Cocoon blocks?</h1>
--- <p>A block is the unit of modularization in Cocoon. It is a Java archive
(jar)
--- that </p>
+++ <p>A block is the unit of modularization (Eclipse uses the term plugins,
OSGi
+++ bundles) in Cocoon. Everything that goes beyond that what Cocoon provides
in its
+++ core is provided as block. Every custom Cocoon application is developed as
+++ block. A block <em>can</em> provide following features:</p>
<ul>
--- <li>can contain a Cocoon application based on a block root sitemap</li>
--- <li>can provide Spring beans (either defined in Spring-style or Avalon
style)
--- </li>
--- <li>can contain Java classes and resources</li>
+++ <li>sitemap services by provide pipelines that can be called by a special
+++ purpose protocol (<tt>block:</tt>) as a special servlet service</li>
+++ <li>general servlet services (any servlet can be managed by the Cocoon
blocks
+++ framework)</li>
+++ <li>component services (Spring beans, Avalon services/components)</li>
+++ <li>a container for classes and resources</li>
</ul>
--- <p>Every functionality that goes beyond that what Cocoon provides in its
core is
--- provided as block. Every custom Cocoon application is developed as
block.</p>
+++ <p>A block is packaged as Java archive (jar) following certain
conventions.</p>
</body>
</html>
