cziegeler 02/05/29 03:57:33
Modified: src/documentation/xdocs/installing updating.xml
Log:
Minor doc update
Revision Changes Path
1.4 +58 -4 xml-cocoon2/src/documentation/xdocs/installing/updating.xml
Index: updating.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/src/documentation/xdocs/installing/updating.xml,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- updating.xml 24 May 2002 14:02:07 -0000 1.3
+++ updating.xml 29 May 2002 10:57:32 -0000 1.4
@@ -24,6 +24,9 @@
of Cocoon. This move has lead to some changes in configuration etc. which are
described
by this document.
</p>
+ <p>In addition there were some disadvantages in the internal architecture of
Cocoon. The
+ new version removes these bottlenecks and gives more flexibility, usability and
performance.
+ </p>
</s1>
<s1 title="Components">
<p>
@@ -53,13 +56,64 @@
from the Store interface.</p>
</s2>
<s2 title="Stream and Event Pipeline">
- <p>This is the only real incompatible change. The internal architecture of
Cocoon
- has changed. In the older version, the processing pipeline constructed by
- a generator, the transformers and a serializer was represented by two
components,
+ <p>This is the only real incompatible change (But don't panic, this will
+ not affect you, well at least only a little bit :). The internal
architecture of Cocoon
+ has changed. In the older version, the processing pipeline - constructed by
+ a generator, the transformers and a serializer - was represented by two
components,
called stream and event pipeline.</p>
<p>For a simpler architecture, enhanced functionality and improved performance,
these components have been combined into one: the processing pipeline.</p>
- <p>Mention changes and update strategy...</p>
+ <p>In addition the map:pipeline element of the sitemap has gained more meaning
+ as it is now possible to configure each map:pipeline section in the sitemap
+ differently. So there can be one section using caching, another one not
+ caching at all and a third one using a different caching implementation etc.
+ </p>
+ <s3 title="Changed Configuration">
+ <p>
+ The configuration of the pipelines has moved from the cocoon.xconf to the
sitemap.
+ So, for updating you have to remove the "event-pipeline" and
"stream-pipeline" section
+ from your cocoon.xconf and add the map:pipelines section to the
map:components section
+ in your sitemap. You can find the pipelines components definition in the
sample
+ sitemap of Cocoon. Here is an example:
+ </p>
+ <source><![CDATA[
+<map:sitemap>
+ <map:components>
+ ...
+ <map:pipelines default="caching">
+ <map:pipeline name="caching"
+
src="org.apache.cocoon.components.pipeline.impl.CachingProcessingPipeline"/>
+ <map:pipeline name="noncaching"
+
src="org.apache.cocoon.components.pipeline.impl.NonCachingProcessingPipeline"/>
+ </map:pipelines>
+ </map:components>
+ ...
+</map:sitemap>
+ ]]></source>
+ <p>The configuration is similar to the configuration of other sitemap
components, like
+ generators or actions. You can choose these different implementations of
pipelines
+ in the map:pipeline section by specifying the type attribute:
+ </p>
+ <source><![CDATA[
+<map:sitemap>
+ ...
+ <map:pipelines>
+ <map:pipeline type="noncaching">
+ <map:match pattern="welcome">
+ ...
+ </map:match>
+ ..
+ </map:pipeline>
+ </map:pipelines>
+</map:sitemap>
+ ]]></source>
+ <p>So again, this is similar to choosing the type of the generator or any
other sitemap
+ component. If you omit the type attribute the default configuration from the
components
+ section is used.
+ </p>
+ <p>So you see, although this is an incompatible change in the Java code, you
have only
+ little to do to update your Cocoon installation.</p>
+ </s3>
</s2>
</s1>
----------------------------------------------------------------------
In case of troubles, e-mail: [EMAIL PROTECTED]
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
