Difference between revisions of "Apache Cocoon"
TroclAeltv (talk | contribs) m (ellalaal) |
Piotr Banski (talk | contribs) m (Reverted edit of TroclAeltv, changed back to last version by Piotr Banski) |
||
Line 1: | Line 1: | ||
− | |||
[[Category:Tools]] | [[Category:Tools]] | ||
[[Category:Publishing and delivery tools]] | [[Category:Publishing and delivery tools]] | ||
Line 17: | Line 16: | ||
Cocoon has been designed to coexist and interoperate side-by-side with your existing J2EE solutions or to give them new functionality without requiring any change in the existing infrastructure. | Cocoon has been designed to coexist and interoperate side-by-side with your existing J2EE solutions or to give them new functionality without requiring any change in the existing infrastructure. | ||
− | Cocoon interacts with many data sources, including filesystems, RDBMS, LDAP, native XML databases, | + | Cocoon interacts with many data sources, including filesystems, RDBMS, LDAP, native XML databases, SAP® systems and network-based data sources. It adapts content delivery to the capabilities of different devices like HTML, WML, PDF, SVG, and RTF, to name just a few. You can run Cocoon as a Servlet as well as through a powerful, commandline interface. The deliberate design of its abstract environment gives you the freedom to extend its functionality to meet your special needs in a highly modular fashion. |
Revision as of 15:54, 5 January 2008
Summary
Apache Cocoon is a web development framework built around the concepts of separation of concerns and component-based web development. The TEI consortium website is dynamically produced from TEI XML using Cocoon.
Description
Apache Cocoon is a web development framework built around the concepts of separation of concerns (making sure people can interact and collaborate on a project, without stepping on each other toes) and component-based web development.
Cocoon implements these concepts around the notion of "component pipelines", each component on the pipeline specializing on a particular operation. This makes it possible to use a "building block" approach for web solutions, hooking together components into pipelines without any required programming.
Cocoon is "web glue for your web application development needs". It is a glue that keeps concerns separate and allows parallel evolution of the two sides, improving development pace and reducing the chance of conflicts.
Cocoon has been designed to coexist and interoperate side-by-side with your existing J2EE solutions or to give them new functionality without requiring any change in the existing infrastructure.
Cocoon interacts with many data sources, including filesystems, RDBMS, LDAP, native XML databases, SAP® systems and network-based data sources. It adapts content delivery to the capabilities of different devices like HTML, WML, PDF, SVG, and RTF, to name just a few. You can run Cocoon as a Servlet as well as through a powerful, commandline interface. The deliberate design of its abstract environment gives you the freedom to extend its functionality to meet your special needs in a highly modular fashion.
Installation Notes
There are many different ways to install Cocoon, and so it is probably best that you look at the Cocoon installation instructions. However, those of you using debian-compatible systems can install a packaged version of cocoon maintained by Sebastian Rahtz. See: http://tei.oucs.ox.ac.uk/teideb/