You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@cocoon.apache.org by re...@apache.org on 2011/01/16 21:35:39 UTC
svn commit: r1059656 -
/cocoon/cocoon3/trunk/cocoon-docs/src/site/apt/index.apt
Author: reinhard
Date: Sun Jan 16 20:35:39 2011
New Revision: 1059656
URL: http://svn.apache.org/viewvc?rev=1059656&view=rev
Log:
fix typos
Modified:
cocoon/cocoon3/trunk/cocoon-docs/src/site/apt/index.apt
Modified: cocoon/cocoon3/trunk/cocoon-docs/src/site/apt/index.apt
URL: http://svn.apache.org/viewvc/cocoon/cocoon3/trunk/cocoon-docs/src/site/apt/index.apt?rev=1059656&r1=1059655&r2=1059656&view=diff
==============================================================================
--- cocoon/cocoon3/trunk/cocoon-docs/src/site/apt/index.apt (original)
+++ cocoon/cocoon3/trunk/cocoon-docs/src/site/apt/index.apt Sun Jan 16 20:35:39 2011
@@ -7,9 +7,9 @@
Apache Cocoon 3
- Apache Cocoon 3 is a major rewrite of Cocoon 2.2. Like Cocoon 2 it is based around the concept of
-pipelines and sitemaps and it is very similar to Cocoon 2.2 in many respects but is slimmed down and
-designed to be <<easily used with Java code>> (= no frameworks required!). On top of this,
+ Apache Cocoon 3 is a major rewrite of Cocoon 2.2. Like Cocoon 2 it is based around the concept of
+pipelines and sitemaps and it is very similar to Cocoon 2.2 in many respects but is slimed down and
+designed to be <<easily used with Java code>> (= no frameworks required!). On top of this,
Cocoon 3 has the goal of becoming the best available platform for <<RESTful webservices>> and web applications.
* Download
@@ -20,7 +20,7 @@ message before using it.
* Using Pipelines in Java has never been so easy
Here is an example that transforms an XML document by reading it from an
- URL, will be processed including linked documents following the <XInclude> reccomandation,
+ URL, will be processed including linked documents following the <XInclude> recommendation,
then will be transformed applying a stylesheet, validated against an XSchema,
and finally serialized:
@@ -37,9 +37,9 @@ pipeline.addComponent(new XMLSerializer(
ByteArrayOutputStream baos = new ByteArrayOutputStream();
pipeline.setup(baos);
pipeline.execute();
-+------------------------------------------+
++------------------------------------------+
- The idea behind using a pipeline for this purpose is that the content of the pipeline (in this case SAX events)
+ The idea behind using a pipeline for this purpose is that the content of the pipeline (in this case SAX events)
is streamed without any necessary serialization or deserialization steps <between> the components.
* Sitemaps and integration with Java Servlets