You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cvs@cocoon.apache.org by gk...@apache.org on 2008/07/16 12:16:20 UTC
svn commit: r677229 - in /cocoon/site/site/2.2: ./ flash/
Author: gkossakowski
Date: Wed Jul 16 03:16:18 2008
New Revision: 677229
URL: http://svn.apache.org/viewvc?rev=677229&view=rev
Log:
Publish some of new docs.
Added:
cocoon/site/site/2.2/1448_1_1.html
cocoon/site/site/2.2/1454_1_1.html
cocoon/site/site/2.2/flash/
cocoon/site/site/2.2/flash/1452_1_1.swf (with props)
Modified:
cocoon/site/site/2.2/1159_1_1.html
cocoon/site/site/2.2/1290_1_1.html
cocoon/site/site/2.2/1291_1_1.html
cocoon/site/site/2.2/1327_1_1.html
cocoon/site/site/2.2/1347_1_1.html
cocoon/site/site/2.2/1362_1_1.html
cocoon/site/site/2.2/1366_1_1.html
cocoon/site/site/2.2/1402_1_1.html
cocoon/site/site/2.2/1420_1_1.html
cocoon/site/site/2.2/1447_1_1.html
cocoon/site/site/2.2/license.html
cocoon/site/site/2.2/project-info.html
cocoon/site/site/2.2/team-list.html
Modified: cocoon/site/site/2.2/1159_1_1.html
URL: http://svn.apache.org/viewvc/cocoon/site/site/2.2/1159_1_1.html?rev=677229&r1=677228&r2=677229&view=diff
==============================================================================
--- cocoon/site/site/2.2/1159_1_1.html (original)
+++ cocoon/site/site/2.2/1159_1_1.html Wed Jul 16 03:16:18 2008
@@ -98,6 +98,10 @@
<li >
<a href="1420_1_1.html">New in 2.2</a>
</li>
+
+ <li >
+ <a href="1454_1_1.html">Test2</a>
+ </li>
</ul>
</li>
<li>
@@ -149,10 +153,10 @@
<li>Import the block as a project in Eclipse</li>
<li>Start the block as a web application and access it from your browser</li>
</ol><div class="note"><div><strong>Note: </strong>First, make sure that you have Maven 2.0.9 or above installed.
-You can check this by calling <tt xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">mvn --version</tt> from the command line. If
+You can check this by calling <tt xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">mvn --version</tt> from the command line. If
this doesn't work for you, read the
<a href="http://maven.apache.org/guides/getting-started/maven-in-five-minutes.html">Maven
-in 5 Minutes</a> tutorial.</div></div><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Creating a Cocoon block</h1>Create a new directory which will be the root directory of your Cocoon
+in 5 Minutes</a> tutorial.</div></div><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Creating a Cocoon block</h1>Create a new directory which will be the root directory of your Cocoon
application and change into it. For this tutorial, let's name it
<tt>getting-started-app</tt>.The next step is to create a Cocoon block to contain your custom application.
The development of any Cocoon web application should be done within one or more
@@ -172,12 +176,12 @@
samples)
3: remote -> cocoon-22-archetype-webapp (Creates a web application configured to
host Cocoon blocks. Just add the block dependencies)
-Choose a number: (1/2/3): <strong xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">2</strong>
+Choose a number: (1/2/3): <strong xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">2</strong>
</pre><p>Maven first asks which archetype you want to create. Item 2 in this list is
-the standard Cocoon block with some small sample files already in place.</p><pre>Define value for groupId: : <strong xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">com.mycompany</strong>
-Define value for artifactId: : <strong xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">myBlock1</strong>
-Define value for version: 1.0-SNAPSHOT: : <strong xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">1.0.0</strong>
-Define value for package: : <strong xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">com.mycompany.myBlock1</strong><strong xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0"><strong>
+the standard Cocoon block with some small sample files already in place.</p><pre>Define value for groupId: : <strong xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">com.mycompany</strong>
+Define value for artifactId: : <strong xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">myBlock1</strong>
+Define value for version: 1.0-SNAPSHOT: : <strong xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">1.0.0</strong>
+Define value for package: : <strong xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">com.mycompany.myBlock1</strong><strong xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher"><strong>
</strong></strong></pre><p>Maven then asks a few more questions. Just enter the details as shown
above. The groupId is a label that you can use to group all the blocks in your
application. The artifactId is the unique label that will identify this block
@@ -186,30 +190,30 @@
in the block will be assigned to.</p><div class="note"><div><strong>Note: </strong>If you are using a cocoon binary build from svn trunk then you
probably want to change the archetypeVersion to the most recent one, matching
the svn trunk. (see
-<tt xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">[<tt>c</tt></tt><tt xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">ocoon-svn]/tools/archetypes/cocoon-22-archetype-block/pom.xml</tt>)
+<tt xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">[<tt>c</tt></tt><tt xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">ocoon-svn]/tools/archetypes/cocoon-22-archetype-block/pom.xml</tt>)
</div></div><p>Looking at the filesystem, you should find following directory structure:</p><pre>getting-started-app
-<tt xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0"> +-</tt><tt xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">myBlock1
+<tt xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher"> +-</tt><tt xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">myBlock1
+-pom.xml
+-src
+-[...]
-</tt></pre><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Import the block in Eclipse</h1><div class="note"><div><strong>Note: </strong>Cocoon is not tied to Eclipse IDE by any means. This step only
+</tt></pre><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Import the block in Eclipse</h1><div class="note"><div><strong>Note: </strong>Cocoon is not tied to Eclipse IDE by any means. This step only
describes what can be done to avoid tedious work of setting up project in
-Eclipse manually.<br xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0"></br>
+Eclipse manually.<br xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher"></br>
If you don't use Eclipse, you can either skip this step or find a similar
procedure to load the block in the IDE of your choice.</div></div><p>Change into the <tt>myBlock1</tt> directory and call</p><pre>mvn eclipse:eclipse</pre><p>This will create the necessary project descriptors for Eclipse. In Eclipse
you can import the project into your workspace: <em>File > Import... >
Existing Projects into Workspace</em></p><p>If that's the first time you use Eclipse together with a project created by
Maven 2, we recommend you read the
<a href="http://maven.apache.org/guides/mini/guide-ide-eclipse.html">Maven Guide
-using Eclipse with Maven 2.x</a>.</p><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Run the block as Java web application</h1><p>After creating the Cocoon block you probably want to run it. For this purpose
+using Eclipse with Maven 2.x</a>.</p><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Run the block as Java web application</h1><p>After creating the Cocoon block you probably want to run it. For this purpose
there is a Maven plugin that generates a minimal web application that loads your
block. The pom.xml of your block already contains the necessary settings.</p><pre>mvn jetty:run</pre><p>and point your browser at <tt>http://localhost:8888/myBlock1/</tt> and get a
hello world page.</p><div class="note"><div><strong>Note: </strong>The mentioned minimal web application is automatically created,
-when <tt xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">mvn jetty:run</tt> is invoked. This happens because the rcl goal of the
+when <tt xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">mvn jetty:run</tt> is invoked. This happens because the rcl goal of the
Cocoon plugin is bound to the Maven build lifecycle which is invoked too, when
-the jetty:run goal is executed. See the block's <tt xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">pom.xml </tt>for details.
-</div></div><div class="note"><div><strong>Note: </strong>This process can be manually triggered with <tt xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">mvn
-cocoon:prepare</tt> too.</div></div><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Conclusion and further information</h1><p>So far you have created a Cocoon block and been able to run it in Jetty.
+the jetty:run goal is executed. See the block's <tt xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">pom.xml </tt>for details.
+</div></div><div class="note"><div><strong>Note: </strong>This process can be manually triggered with <tt xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">mvn
+cocoon:prepare</tt> too.</div></div><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Conclusion and further information</h1><p>So far you have created a Cocoon block and been able to run it in Jetty.
This is only the first step to creating a full-blown Cocoon application. If you
would like to know more read the following tutorials:</p><ul>
<li><a href="1290_1_1.html">Your first XML pipeline</a><br></br>
Modified: cocoon/site/site/2.2/1290_1_1.html
URL: http://svn.apache.org/viewvc/cocoon/site/site/2.2/1290_1_1.html?rev=677229&r1=677228&r2=677229&view=diff
==============================================================================
--- cocoon/site/site/2.2/1290_1_1.html (original)
+++ cocoon/site/site/2.2/1290_1_1.html Wed Jul 16 03:16:18 2008
@@ -98,6 +98,10 @@
<li >
<a href="1420_1_1.html">New in 2.2</a>
</li>
+
+ <li >
+ <a href="1454_1_1.html">Test2</a>
+ </li>
</ul>
</li>
<li>
@@ -119,6 +123,10 @@
<li >
<a href="1362_1_1.html">Deploying a Cocoon application</a>
</li>
+
+ <li >
+ <a href="1448_1_1.html">Screencasts</a>
+ </li>
</ul>
</li>
<li>
@@ -148,7 +156,7 @@
<li>enhance this first pipeline by adding an XML transformation step based on
XSLT that produces HTML as output</li>
<li>write a pipeline that creates a PDF document</li>
-</ol><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Overview</h1>Cocoon is based around the concept of pipelines:<img width="713" height="223" name="pipeline" alt="pipeline" src="NO_LINK"></img>If a request comes in, a <a href="../2.2/core-modules/core/2.2/850_1_1.html"><strong>generator</strong>
+</ol><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Overview</h1>Cocoon is based around the concept of pipelines:<img width="713" height="223" name="pipeline" alt="pipeline" src="NO_LINK"></img>If a request comes in, a <a href="../2.2/core-modules/core/2.2/850_1_1.html"><strong>generator</strong>
</a>produces <a href="http://www.saxproject.org/">SAX events</a> that represent
the XML, <a href="../2.2/core-modules/core/2.2/851_1_1.html"><strong>tranformers</strong> </a>can alter the
stream of SAX events and a
@@ -160,7 +168,7 @@
</ul><strong>Sitemaps</strong> are used to define those pipelines and connect them
with requests. These connections are defined by some kind of rules. In the
context of Cocoon those rules are named matchers. Whenever one of those rules
-(<em>matcher</em>) matches, a pipeline is executed.<h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Create a pipeline in the sitemap</h1>First, open <tt>src\main\resources\COB-INF\sitemap.xmap</tt> in your favorite
+(<em>matcher</em>) matches, a pipeline is executed.<h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Create a pipeline in the sitemap</h1>First, open <tt>src\main\resources\COB-INF\sitemap.xmap</tt> in your favorite
XML editor. That's your block's base sitemap. There are already some pipelines
there (<tt>/sitemap/pipelines</tt>) but for the sake of this tutorial, let's
create your own pipeline.<pre><map:sitemap xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
@@ -169,7 +177,7 @@
xmlns:map="http://apache.org/cocoon/sitemap/1.0">
<map:pipelines>
-<strong xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0"> <map:pipeline>
+<strong xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher"> <map:pipeline>
<strong> <map:match pattern="myFirstPipeline">
<map:generate src="myXmlFile.xml" type="file"/>
<map:serialize type="xml"/>
@@ -186,13 +194,13 @@
directory as the sitemap:<pre><?xml version="1.0" encoding="UTF-8"?>
<content>test</content>
</pre><div class="note"><div><strong>Note: </strong>You might wonder why the matcher only has to look for the
-pattern myFirstPipeline. The reason is that <tt xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">myBlock1</tt> is handled by the
+pattern myFirstPipeline. The reason is that <tt xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">myBlock1</tt> is handled by the
block dispatching mechanism. In particular for your block, this path is set in
-<tt xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">src/main/resources/META-INF/cocoon/spring/servlet-service.xml</tt> in
-<tt xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">/beans/bean[id='com.mycompany.myBlock4.block']/context/@mount-path</tt></div></div><p>After saving the sitemap and the XML file, you can point you browser to
+<tt xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">src/main/resources/META-INF/cocoon/spring/servlet-service.xml</tt> in
+<tt xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">/beans/bean[id='com.mycompany.myBlock4.block']/context/@mount-path</tt></div></div><p>After saving the sitemap and the XML file, you can point you browser to
<tt>http://localhost:8888/myBlock</tt><tt><tt>1</tt>/myFirstPipeline</tt> and
you will see the output of your first own pipeline serialized as XML
-(<tt><map:serialize type="xml"/></tt>).</p><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Adding an XSLT transformation step</h1><p>The first pipeline wasn't really exciting, just reading some XML file and
+(<tt><map:serialize type="xml"/></tt>).</p><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Adding an XSLT transformation step</h1><p>The first pipeline wasn't really exciting, just reading some XML file and
serializing it without changing anything. The second example will add a
transformation step based on <a href="http://www.w3.org/TR/xslt">XSLT</a>:</p><pre><map:sitemap xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://apache.org/cocoon/sitemap/1.0
@@ -204,7 +212,7 @@
<map:match pattern="myFirstPipeline">
<map:generate src="myXmlFile.xml" type="file"/>
<map:serialize type="xml"/>
- </map:match> <strong xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0"><strong><strong>
+ </map:match> <strong xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher"><strong><strong>
<map:match pattern="mySecondPipeline">
<map:generate src="myXmlFile.xml" type="file"/>
</strong></strong><strong><strong><strong><strong> <map:transform src="myXsltFile.xslt" type="xslt"/></strong></strong></strong></strong>
@@ -234,13 +242,13 @@
serializer.</p><div class="note"><div><strong>Note: </strong>In this tutorial you have already implemented two pipelines but
there is only one pipeline element used in the sitemap. Given this is confusing
when you use Cocoon sitemaps the first time. However, there is a reason for
-this: The <tt xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0"><pipeline> </tt>element indicates which <em xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">pipeline
-implementation</em> is used. If there is no <tt xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">@type</tt> attribute, the
+this: The <tt xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher"><pipeline> </tt>element indicates which <em xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">pipeline
+implementation</em> is used. If there is no <tt xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">@type</tt> attribute, the
generators, tranformers and serializers are invoked from a caching pipeline
-implementation. <br xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0"></br>
+implementation. <br xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher"></br>
When Cocoon developers talk about pipelines, they mean a series of a matcher
that includes at least a generator and a serializer. Transformers and other
-sitemap components are optional.</div></div><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Creating a PDF</h1><p>The first example created XML and the second one HTML. One of the strength of
+sitemap components are optional.</div></div><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Creating a PDF</h1><p>The first example created XML and the second one HTML. One of the strength of
Cocoon is that it makes it very simple to support many different output formats.
The result of this third example will be a PDF, again based on
<em>myXmlFile.xml</em>:</p><pre><map:sitemap xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
@@ -258,7 +266,7 @@
<map:generate src="myXmlFile.xml" type="file"/>
<map:transform src="myXsltFile.xslt" type="xslt"/>
<map:serialize type="html"/>
- </map:match> <strong xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0"><strong><strong>
+ </map:match> <strong xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher"><strong><strong>
<map:match pattern="myThirdPipeline">
<map:generate src="myXmlFile.xml" type="file"/>
</strong></strong><strong><strong><strong><strong> <map:transform src="myXml2PdfFile.xslt" type="xslt"/></strong></strong></strong></strong>
@@ -327,9 +335,9 @@
pom.xml of your block:</p><pre> <dependencies>
[...]
<dependency>
- <groupId><strong xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">org.apache.cocoon</strong></groupId>
- <artifactId><strong xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">cocoon-fop-impl</strong></artifactId>
- <version><strong xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">1.0.0</strong></version>
+ <groupId><strong xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">org.apache.cocoon</strong></groupId>
+ <artifactId><strong xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">cocoon-fop-impl</strong></artifactId>
+ <version><strong xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">1.0.0</strong></version>
</dependency>
[...]
</dependencies></pre><p>Rebuild your block</p><pre>mvn compile</pre><p>and start the servlet container again:</p><pre>mvn jetty:run</pre><p>Now you can point your browser at
Modified: cocoon/site/site/2.2/1291_1_1.html
URL: http://svn.apache.org/viewvc/cocoon/site/site/2.2/1291_1_1.html?rev=677229&r1=677228&r2=677229&view=diff
==============================================================================
--- cocoon/site/site/2.2/1291_1_1.html (original)
+++ cocoon/site/site/2.2/1291_1_1.html Wed Jul 16 03:16:18 2008
@@ -98,6 +98,10 @@
<li >
<a href="1420_1_1.html">New in 2.2</a>
</li>
+
+ <li >
+ <a href="1454_1_1.html">Test2</a>
+ </li>
</ul>
</li>
<li>
@@ -153,7 +157,7 @@
<li>connect one block with another one</li>
<li>use a pipeline fragement available in one block from within another block
</li>
-</ol><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Create a second block</h1>For this purpose move into the <tt>getting-started-app</tt> directory and use
+</ol><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Create a second block</h1>For this purpose move into the <tt>getting-started-app</tt> directory and use
the Maven 2 archetype command again:<pre>mvn archetype:generate -DarchetypeCatalog=http://cocoon.apache.org
</pre>First choose the archetype:<pre>Choose archetype:
1: remote -> cocoon-22-archetype-block-plain (Creates an empty Cocoon block; useful
@@ -162,24 +166,24 @@
samples)
3: remote -> cocoon-22-archetype-webapp (Creates a web application configured to
host Cocoon blocks. Just add the block dependencies)
-Choose a number: (1/2/3): <strong xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">2
-</strong></pre>Then respond to the other questions as follows:<pre>Define value for groupId: : <strong xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">com.mycompany</strong>
-Define value for artifactId: : <strong xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">myBlock2</strong>
-Define value for version: 1.0-SNAPSHOT: : <strong xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">1.0.0</strong>
-Define value for package: : <strong xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">com.mycompany.myBlock2</strong></pre><p>The result is a second Cocoon block called myBlock2. You should find the
+Choose a number: (1/2/3): <strong xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">2
+</strong></pre>Then respond to the other questions as follows:<pre>Define value for groupId: : <strong xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">com.mycompany</strong>
+Define value for artifactId: : <strong xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">myBlock2</strong>
+Define value for version: 1.0-SNAPSHOT: : <strong xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">1.0.0</strong>
+Define value for package: : <strong xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">com.mycompany.myBlock2</strong></pre><p>The result is a second Cocoon block called myBlock2. You should find the
directory structure of your application now looks as follows:</p><pre>getting-started-app
-<tt xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0"> +-</tt><tt xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">myBlock1
+<tt xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher"> +-</tt><tt xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">myBlock1
| +-pom.xml
| +-src
| +-[...]</tt>
-<tt xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0"> +-</tt><tt xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">myBlock2
+<tt xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher"> +-</tt><tt xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">myBlock2
+-pom.xml
+-src
+-[...]
</tt></pre><p>Move into the myBlock2 folder and execute the following command:</p><pre>mvn install eclipse:eclipse</pre><p>This builds and copies the second block into your local Maven repository so
that other dependent blocks and projects can see it and then creates the
-necessary files to allow you to import the block as a project in Eclipse.</p><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Connect two blocks</h1><p>Let's assume that you want to use a pipeline defined in <tt>myBlock2</tt>
+necessary files to allow you to import the block as a project in Eclipse.</p><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Connect two blocks</h1><p>Let's assume that you want to use a pipeline defined in <tt>myBlock2</tt>
from within <tt>myBlock1</tt>. You have to establish the connection between the
two blocks. Edit
<tt>getting-started-app/<strong>myBlock1</strong>/src/main/resources/META-INF/cocoon/spring/block-servlet-service.xml:</tt>
@@ -192,7 +196,7 @@
<bean id="com.mycompany.myBlock1.service" class="org.apache.cocoon.sitemap.SitemapServlet">
<servlet:context mount-path="/myBlock1" context-path="blockcontext:/myBlock1/">
-<strong xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0"> <servlet:connections>
+<strong xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher"> <servlet:connections>
<entry key="myBlock2" value-ref="com.mycompany.myBlock2.service"/>
</servlet:connections></strong>
</servlet:context>
@@ -206,7 +210,7 @@
[...]
<dependencies>
[...]
-<strong xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0"> <dependency>
+<strong xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher"> <dependency>
<groupId>com.mycompany</groupId>
<artifactId>myBlock2</artifactId>
<version>1.0-SNAPSHOT</version>
@@ -219,7 +223,7 @@
advantage that you can work on block2 and the changes take effect immediatly.
Open getting-started-app/myBlock1/rcl.properties and add</p><pre>com.mycompany.myBlock1.service%classes-dir=./target/classes
-<strong xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">com.mycompany.myBlock2.service%classes-dir=../myBlock2/target/classes
+<strong xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">com.mycompany.myBlock2.service%classes-dir=../myBlock2/target/classes
%exclude-lib=com.mycompany:myBlock2
</strong></pre><p>Restart the servlet container by invoking</p><pre>mvn jetty:run
</pre><p>Now it's time to test connection. For that purpose add a pipeline to the
@@ -231,7 +235,7 @@
[...]
<map:pipeline>
<map:match pattern="callingBlock2">
- <map:generate src="<strong xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">servlet:myBlock2:/spring-bean</strong>" type="file"/>
+ <map:generate src="<strong xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">servlet:myBlock2:/spring-bean</strong>" type="file"/>
<map:serialize type="xml"/>
</map:match>
</map:pipeline>
@@ -245,7 +249,7 @@
<br></br>
Though this is a "<em>hello word</em>" style example you might already imagine
the power of this protocol, e.g. you can move all styling resources and
-pipelines to a particular block.</p><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Use a pipeline fragment</h1><p>The previous example showed how you can call a pipeline from another block.
+pipelines to a particular block.</p><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Use a pipeline fragment</h1><p>The previous example showed how you can call a pipeline from another block.
But here is even more you can do! A sitemap can also provide pipeline fragements
that can be used by other blocks:</p><pre><?xml version="1.0" encoding="UTF-8"?>
<map:sitemap xmlns:map="http://apache.org/cocoon/sitemap/1.0">
@@ -253,7 +257,7 @@
<map:pipeline>
<map:match pattern="callingTransformationService">
<map:generate src="demo/welcome.xml"/>
- <strong xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0"><map:transform type="servletService">
+ <strong xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher"><map:transform type="servletService">
<map:parameter name="service"
value="servlet:myBlock2:/myXsltTransformation-service"/>
</map:transform></strong>
@@ -271,8 +275,8 @@
<map:sitemap xmlns:map="http://apache.org/cocoon/sitemap/1.0">
<map:pipelines>
<map:pipeline>
- <map:match pattern="<strong xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">myXsltTransformation-service</strong>">
- <map:generate src="<strong xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">service-consumer:</strong>"/>
+ <map:match pattern="<strong xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">myXsltTransformation-service</strong>">
+ <map:generate src="<strong xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">service-consumer:</strong>"/>
<map:transform src="myXsltTransformation.xslt"/>
<map:serialize type="xml"/>
</map:match>
Modified: cocoon/site/site/2.2/1327_1_1.html
URL: http://svn.apache.org/viewvc/cocoon/site/site/2.2/1327_1_1.html?rev=677229&r1=677228&r2=677229&view=diff
==============================================================================
--- cocoon/site/site/2.2/1327_1_1.html (original)
+++ cocoon/site/site/2.2/1327_1_1.html Wed Jul 16 03:16:18 2008
@@ -98,6 +98,10 @@
<li >
<a href="1420_1_1.html">New in 2.2</a>
</li>
+
+ <li >
+ <a href="1454_1_1.html">Test2</a>
+ </li>
</ul>
</li>
<li>
@@ -119,6 +123,10 @@
<li >
<a href="1362_1_1.html">Deploying a Cocoon application</a>
</li>
+
+ <li >
+ <a href="1448_1_1.html">Screencasts</a>
+ </li>
</ul>
</li>
<li>
Modified: cocoon/site/site/2.2/1347_1_1.html
URL: http://svn.apache.org/viewvc/cocoon/site/site/2.2/1347_1_1.html?rev=677229&r1=677228&r2=677229&view=diff
==============================================================================
--- cocoon/site/site/2.2/1347_1_1.html (original)
+++ cocoon/site/site/2.2/1347_1_1.html Wed Jul 16 03:16:18 2008
@@ -98,6 +98,10 @@
<li >
<a href="1420_1_1.html">New in 2.2</a>
</li>
+
+ <li >
+ <a href="1454_1_1.html">Test2</a>
+ </li>
</ul>
</li>
<li>
@@ -119,6 +123,10 @@
<li >
<a href="1362_1_1.html">Deploying a Cocoon application</a>
</li>
+
+ <li >
+ <a href="1448_1_1.html">Screencasts</a>
+ </li>
</ul>
</li>
<li>
Modified: cocoon/site/site/2.2/1362_1_1.html
URL: http://svn.apache.org/viewvc/cocoon/site/site/2.2/1362_1_1.html?rev=677229&r1=677228&r2=677229&view=diff
==============================================================================
--- cocoon/site/site/2.2/1362_1_1.html (original)
+++ cocoon/site/site/2.2/1362_1_1.html Wed Jul 16 03:16:18 2008
@@ -98,6 +98,10 @@
<li >
<a href="1420_1_1.html">New in 2.2</a>
</li>
+
+ <li >
+ <a href="1454_1_1.html">Test2</a>
+ </li>
</ul>
</li>
<li>
@@ -157,7 +161,7 @@
modules from a single command)</li>
<li>Change the block mount point so that it is mounted at the root level context
(typical for a web application's "main block")</li>
-</ol><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Creating a Cocoon web application</h1>For this tutorial you will use the Cocoon web application archetype to create
+</ol><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Creating a Cocoon web application</h1>For this tutorial you will use the Cocoon web application archetype to create
a Cocoon block suitable for generating a war file which can be deployed on a
servlet container such as Tomcat or Websphere etc. Change into the
getting-started-app folder and type the following command: -<pre>mvn archetype:generate -DarchetypeCatalog=http://cocoon.apache.org
@@ -168,25 +172,25 @@
samples)
3: remote -> cocoon-22-archetype-webapp (Creates a web application configured to
host Cocoon blocks. Just add the block dependencies)
-Choose a number: (1/2/3): <strong xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">3
-</strong></pre>Then respond to the other questions as follows:<pre>Define value for groupId: : <strong xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">com.mycompany</strong>
-Define value for artifactId: : <strong xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">myCocoonWebApp</strong>
-Define value for version: 1.0-SNAPSHOT: : <strong xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">1.0.0</strong>
-Define value for package: : <strong xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">com.mycompany.myCocoonWebApp</strong>
+Choose a number: (1/2/3): <strong xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">3
+</strong></pre>Then respond to the other questions as follows:<pre>Define value for groupId: : <strong xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">com.mycompany</strong>
+Define value for artifactId: : <strong xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">myCocoonWebApp</strong>
+Define value for version: 1.0-SNAPSHOT: : <strong xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">1.0.0</strong>
+Define value for package: : <strong xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">com.mycompany.myCocoonWebApp</strong>
</pre><p>Looking at the filesystem, you should find following directory structure:</p><pre>getting-started-app
-<tt xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0"> +-</tt><tt xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">myBlock1
+<tt xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher"> +-</tt><tt xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">myBlock1
| +-pom.xml
| +-src
| +-[...]
-</tt><tt xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0"> +-</tt><tt xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">myBlock2
+</tt><tt xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher"> +-</tt><tt xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">myBlock2
| +-pom.xml
| +-src
| +-[...]</tt>
-<tt xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0"> +-</tt><tt xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0"><tt>myCocoonWebapp</tt></tt><tt xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">
+<tt xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher"> +-</tt><tt xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher"><tt>myCocoonWebapp</tt></tt><tt xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">
+-pom.xml
+-src
+-[...]</tt>
-</pre><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Using a block within the web application</h1><p>In order to use blocks as dependencies you need to <em>install</em> them into
+</pre><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Using a block within the web application</h1><p>In order to use blocks as dependencies you need to <em>install</em> them into
Maven's local repository. First go to <tt>myBlock1/</tt> directory and execute
following command:</p><pre>mvn install
</pre><p>Then go to <tt>myBlock2/</tt> and execute the same command. This way both
@@ -199,12 +203,12 @@
[...]
<dependencies>
<dependency>
-<strong xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0"> <groupId><strong><tt>com.mycompany</tt></strong></groupId>
+<strong xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher"> <groupId><strong><tt>com.mycompany</tt></strong></groupId>
<artifactId><strong>myBlock1</strong></artifactId>
<version><strong>1.0-SNAPSHOT</strong></version></strong>
</dependency>
<dependency>
-<strong xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0"> <groupId><strong><tt>com.mycompany</tt></strong></groupId>
+<strong xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher"> <groupId><strong><tt>com.mycompany</tt></strong></groupId>
<artifactId><strong>myBlock2</strong></artifactId>
<version><strong>1.0-SNAPSHOT</strong></version></strong>
</dependency>
@@ -212,7 +216,7 @@
[...]
</project></pre><p>That's it. Now it's time to run the web application. Move into
<tt>getting-started-app/myCocoonWebapp</tt> and call</p><pre>mvn package jetty:run</pre><p>from there.<br></br>
-Open your favorite web browser and call</p><pre>http://localhost:8888/myBlock1/</pre><p>That's it!</p><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Creating a parent pom</h1><p>For your convenience you can create a parent pom for the three Maven modules.
+Open your favorite web browser and call</p><pre>http://localhost:8888/myBlock1/</pre><p>That's it!</p><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Creating a parent pom</h1><p>For your convenience you can create a parent pom for the three Maven modules.
Create a file <tt>getting-started-app/pom.xml</tt> with following content:</p><pre><project xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
@@ -227,9 +231,9 @@
<name>Cocoon Getting Stared application [parent]</name>
<modules>
- <module><strong xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0"><tt>myCocoonWebapp</tt></strong></module>
- <module><strong xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">myBlock1</strong></module>
- <module><strong xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">myBlock2</strong></module>
+ <module><strong xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher"><tt>myCocoonWebapp</tt></strong></module>
+ <module><strong xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">myBlock1</strong></module>
+ <module><strong xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">myBlock2</strong></module>
</modules>
</project>
</pre><p>Having a parent pom file, you can trigger a reactor build from root, e.g. you
@@ -244,21 +248,21 @@
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
[...]
-<strong xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0"> <parent>
+<strong xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher"> <parent>
<groupId>com.mycompany</groupId>
<artifactId>getting-started-app</artifactId>
<version>1-SNAPSHOT</version>
</parent></strong>
[...]
-</project></pre><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Mounting your block at the root level</h1><p>You can mount your block at the root level in the application URI space, so
+</project></pre><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Mounting your block at the root level</h1><p>You can mount your block at the root level in the application URI space, so
that instead of using (for example) the URI
<tt>http://localhost:8888/myBlock1/foo/bar</tt> to request a page, you would
request it at <tt>http://localhost:8888/foo/bar</tt>.</p><p>To do this, edit
<tt>myBlock1/src/main/resources/META-INF/cocoon/spring/blockServlet.xml </tt>,
and change the element</p><pre> <property name="mountPath" value="/myBlock1"/>
</pre><p>to</p><pre> <property name="mountPath" value=""/>
-</pre><p>and then run:</p><pre> <tt xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">mvn install</tt></pre></div><div class="editUrl"><div><em>Errors and Improvements?</em> If you see any errors or potential improvements in this document please help
+</pre><p>and then run:</p><pre> <tt xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">mvn install</tt></pre></div><div class="editUrl"><div><em>Errors and Improvements?</em> If you see any errors or potential improvements in this document please help
us: <a href="http://cocoon.zones.apache.org/daisy/cdocs/1362?branch=1&language=1">View, Edit or comment</a> on the latest development version (registration required).
</div></div></div>
</div>
Modified: cocoon/site/site/2.2/1366_1_1.html
URL: http://svn.apache.org/viewvc/cocoon/site/site/2.2/1366_1_1.html?rev=677229&r1=677228&r2=677229&view=diff
==============================================================================
--- cocoon/site/site/2.2/1366_1_1.html (original)
+++ cocoon/site/site/2.2/1366_1_1.html Wed Jul 16 03:16:18 2008
@@ -98,6 +98,10 @@
<li >
<a href="1420_1_1.html">New in 2.2</a>
</li>
+
+ <li >
+ <a href="1454_1_1.html">Test2</a>
+ </li>
</ul>
</li>
<li>
@@ -119,6 +123,10 @@
<li >
<a href="1362_1_1.html">Deploying a Cocoon application</a>
</li>
+
+ <li >
+ <a href="1448_1_1.html">Screencasts</a>
+ </li>
</ul>
</li>
<li>
@@ -146,7 +154,7 @@
UTF-8 with that one, but note that this guide was only tested with UTF-8, other
encodings might not be supported at all places.</div></div><p>The following how-to covers the typical steps to achieve a consistent
encoding throughout a Cocoon application. Some <a href="#theory">Background
-information</a> can be found at the end of this page.</p><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">1. Sending all pages in UTF-8</h1><p>You need to configure Cocoon's serializers to UTF-8. The XML serializer
+information</a> can be found at the end of this page.</p><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">1. Sending all pages in UTF-8</h1><p>You need to configure Cocoon's serializers to UTF-8. The XML serializer
(<tt><serialize type="xml" /></tt>) and the HTML serializer
(<tt><serialize type="html" /></tt>) need to be configured. To support all
browsers, you must state the encoding to be used for the body and also include a
@@ -168,14 +176,14 @@
<doctype-public>-//W3C//DTD HTML 4.01 Transitional//EN</doctype-public>
<doctype-system>http://www.w3.org/TR/html4/loose.dtd</doctype-system>
</serializer>
-</pre><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">2. AJAX Requests with CForms/Dojo</h1><p>If you use CForms with ajax enabled, Cocoon will make use of dojo.io.bind()
+</pre><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">2. AJAX Requests with CForms/Dojo</h1><p>If you use CForms with ajax enabled, Cocoon will make use of dojo.io.bind()
under the hood, which creates XMLHttpRequests that POST the form data to the
server. Here Dojo decides the encoding by default, which does not match the
browser's behaviour of using the charset defined in the META tag. But you can
easily tell Dojo which formatting to use for all dojo.io.bind() calls, just
include that in the top of your HTML pages, before dojo.js is included:</p><pre><script>djConfig = { bindEncoding: "utf-8" };</script>
</pre><p>You might already have other djConfig options, then simply add the
-<tt>bindEncoding</tt> property to the hash map.</p><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">3. Decoding incoming requests: Servlet Container</h1><p>When the browser sends stuff to your server, eg. form data, the
+<tt>bindEncoding</tt> property to the hash map.</p><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">3. Decoding incoming requests: Servlet Container</h1><p>When the browser sends stuff to your server, eg. form data, the
<tt>ServletRequest</tt> will be created by your servlet container, which needs
to decode the parameters correctly into Java Strings. If there is the encoding
specified in the HTTP request header, he will use that, but unfortunately this
@@ -224,16 +232,16 @@
</pre><p>For 2.3 you need to modify the DOCTYPE declaration in the web.xml:</p><pre><!DOCTYPE web-app
PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN"
"http://java.sun.com/dtd/web-app_2_3.dtd">
-</pre><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">4. Setting Cocoon's encoding (especially CForms)</h1><p>To tell Cocoon to use UTF-8 internally, you have to set 2 properties:</p><pre>org.apache.cocoon.containerencoding=utf-8
+</pre><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">4. Setting Cocoon's encoding (especially CForms)</h1><p>To tell Cocoon to use UTF-8 internally, you have to set 2 properties:</p><pre>org.apache.cocoon.containerencoding=utf-8
org.apache.cocoon.formencoding=utf-8
</pre><p>They need to be in some <tt>*.properties</tt> file under
<tt>META-INF/cocoon/properties</tt> in one of your blocks. Note that the
containerencoding must be the same as the one you specified in the
-SetCharacterEncodingFilter. But here we are using UTF-8 everywhere anyway.</p><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">5. XML Files</h1><p>This is normally not a problem, since the standard encoding for XML files is
+SetCharacterEncodingFilter. But here we are using UTF-8 everywhere anyway.</p><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">5. XML Files</h1><p>This is normally not a problem, since the standard encoding for XML files is
UTF-8. However, they should always start with the following instruction, which
should force your XML Editor to save them in UTF-8 (it looks like most of them
do that, so there should not be a problem here).</p><pre><?xml version="1.0" encoding="UTF-8"?>
-</pre><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">6. Special Transformers</h1><p>The standard XSLT Transformers and others are working on SAX events, which
+</pre><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">6. Special Transformers</h1><p>The standard XSLT Transformers and others are working on SAX events, which
are not serialized, thus encoding is not a problem. But there are some special
transformers that pass stuff on to another library that does include
serialization and might need a hint to use the correct encoding. One problem is
@@ -242,12 +250,12 @@
</p><p>If you think there might be a transformer doing things wrong in your
pipeline, add a <tt>TeeTransformer</tt> between each step, outputting the XML
between the transformers into temp1.xml, temp2.xml and so on to look for the
-place where your umlaute and special characters are messed up.</p><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">7. Your own XML serializing Sources</h1><p>If you have your own Source implementation that needs to serialize XML, make
+place where your umlaute and special characters are messed up.</p><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">7. Your own XML serializing Sources</h1><p>If you have your own Source implementation that needs to serialize XML, make
sure it will do that in UTF-8 as well. A good idea is to use Cocoon's XML
serializer, since we already configured that one to UTF-8 above. Sample code
that does that is here:
<a href="http://wiki.apache.org/cocoon/UseCocoonXMLSerializerCode">UseCocoonXMLSerializerCode</a>
-</p><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Further information</h1><h2 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Browser encoding basics</h2><h3 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Getting pages</h3><p>If your Cocoon application needs to read request parameters that could
+</p><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Further information</h1><h2 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Browser encoding basics</h2><h3 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Getting pages</h3><p>If your Cocoon application needs to read request parameters that could
contain <em>special</em> characters, i.e. characters outside of the first 128
ASCII characters, you'll need to pay attention to what encoding is used.</p><p>Normally a browser will send data to the server using the same encoding as
the page containing the submitted form (or whatever). So if the pages are
@@ -258,7 +266,7 @@
</pre><p>or from the HTTP Header Content-Type:</p><pre>Content-Type: text/html; charset=UTF-8
</pre><p>One has to include both to support all browsers. This will be done by the
HTML serializer if you configure it with the parameters mime-type and encoding,
-as stated above.</p><h3 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Sending form data</h3><p>By default, if the browser doesn't explicitely mention the encoding, a
+as stated above.</p><h3 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Sending form data</h3><p>By default, if the browser doesn't explicitely mention the encoding, a
servlet container will decode request parameters using the ISO-8859-1 encoding
(independent of the platform on which the container is running). So in the above
case where UTF-8 was used when serializing, we would be facing problems. An
@@ -274,7 +282,7 @@
character encoding correctly) and then be forwarded to Cocoon, while other times
the processing could start immediately in the Cocoon servlet. It would then be
impossible to know in Cocoon whether the request parameter encoding needs to be
-corrected or not (see below).</p><h2 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Request parameter decoding in Cocoon</h2><h3 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Fixing a wrong servlet container</h3><p>If you are not able to set the default encoding for your servlet container to
+corrected or not (see below).</p><h2 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Request parameter decoding in Cocoon</h2><h3 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Fixing a wrong servlet container</h3><p>If you are not able to set the default encoding for your servlet container to
what you actually want, it is possible to configure Cocoon to re-decode
parameters properly. Suppose the servlet container has ISO-8859-1 default
encoding set, but the requests from the browser are actually encoded in UTF-8.
@@ -290,7 +298,7 @@
JSPGenerator, that access the original HttpServletRequest object and thus do not
get the correctly re-decoded parameter values (that is, if for example the JSP
page itself would read request parameters). The only working solution seems to
-be the servlet-filter here.</p><h3 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Locally overriding the form-encoding</h3><p>Cocoon is ideally suited for publishing to different kinds of devices, and it
+be the servlet-filter here.</p><h3 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Locally overriding the form-encoding</h3><p>Cocoon is ideally suited for publishing to different kinds of devices, and it
may well be possible that for certain devices, it is required to use different
encodings. In this case, you can redefine the form-encoding for specific
pipelines using the SetCharacterEncodingAction.</p><p>To use it, first of all make sure the action is declared in the map:actions
@@ -298,14 +306,14 @@
</pre><p>and then call the action at the required location as follows:</p><pre><map:act type="set-encoding">
<map:parameter name="form-encoding" value="some-other-encoding"/>
</map:act>
-</pre><h2 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Operating System Preliminaries</h2><p>Not having influence on request parameter decoding, but sometimes making
+</pre><h2 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Operating System Preliminaries</h2><p>Not having influence on request parameter decoding, but sometimes making
trouble with text files, database communication, etc. are operating system
language settings. Working with non-english characters may pose problems, as the
JVM seems to detect the system language. If, e.g., german umlauts should be
correctly processed with Cocoon on Linux, it is required to set the LANG
environment variable to de like this:</p><p><tt>export LANG=de</tt></p><p>That's one of several ways of setting the JVM locale, see also
<a href="http://wiki.apache.org/cocoon/SettingTheJvmLocale">SettingTheJvmLocale</a>.
-</p><h2 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">More readings</h2><ul>
+</p><h2 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">More readings</h2><ul>
<li>
<a href="http://marc.theaimsgroup.com/?t=106760662600010&r=1&w=2">Cocoon's
Modified: cocoon/site/site/2.2/1402_1_1.html
URL: http://svn.apache.org/viewvc/cocoon/site/site/2.2/1402_1_1.html?rev=677229&r1=677228&r2=677229&view=diff
==============================================================================
--- cocoon/site/site/2.2/1402_1_1.html (original)
+++ cocoon/site/site/2.2/1402_1_1.html Wed Jul 16 03:16:18 2008
@@ -98,6 +98,10 @@
<li >
<a href="1420_1_1.html">New in 2.2</a>
</li>
+
+ <li >
+ <a href="1454_1_1.html">Test2</a>
+ </li>
</ul>
</li>
<li>
@@ -119,6 +123,10 @@
<li >
<a href="1362_1_1.html">Deploying a Cocoon application</a>
</li>
+
+ <li >
+ <a href="1448_1_1.html">Screencasts</a>
+ </li>
</ul>
</li>
<li>
Modified: cocoon/site/site/2.2/1420_1_1.html
URL: http://svn.apache.org/viewvc/cocoon/site/site/2.2/1420_1_1.html?rev=677229&r1=677228&r2=677229&view=diff
==============================================================================
--- cocoon/site/site/2.2/1420_1_1.html (original)
+++ cocoon/site/site/2.2/1420_1_1.html Wed Jul 16 03:16:18 2008
@@ -98,6 +98,10 @@
<li >
<strong>New in 2.2</strong>
</li>
+
+ <li >
+ <a href="1454_1_1.html">Test2</a>
+ </li>
</ul>
</li>
<li>
@@ -119,6 +123,10 @@
<li >
<a href="1362_1_1.html">Deploying a Cocoon application</a>
</li>
+
+ <li >
+ <a href="1448_1_1.html">Screencasts</a>
+ </li>
</ul>
</li>
<li>
@@ -142,7 +150,7 @@
</ul>
<div id="contentBody"><div id="bodyText"><h1 class="docTitle">New in 2.2</h1><p>While developing Cocoon 2.2 the main goal was simplicity, modularity and
consistent configuration. This page is a summary of all the new features and
-improvements.</p><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">General</h1><ul>
+improvements.</p><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">General</h1><ul>
<li>Cocoon 2.2 doesn't use an Avalon-based component manager any more but uses
Spring 2 instead.</li>
<li>Cocoon components (sitemap components as well as general components) can be
@@ -159,7 +167,7 @@
<li>Cocoon 2.2 uses Comons Logging instead of Avalon Logkit as logging interface
and Log4j as logging implementation. (<em>Also see the 'Incompatibles changes'
section of this document.</em>)</li>
-</ul><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Modularity</h1><ul>
+</ul><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Modularity</h1><ul>
<li>In order to make Cocoon applications more modular, the
Servlet-Service-Framework was introduced. The Servlet-Service-Framework is a
general-purpose framework that makes it possible to establish contracts between
@@ -169,7 +177,7 @@
<li>The Servlet-Service-Framework has no dependency on the 'traditional' Cocoon
(sitemap/pipeline machinery) and can be used together with any
JavaServlet-compatible web application.</li>
-</ul><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Configuration and Deployment</h1><ul>
+</ul><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Configuration and Deployment</h1><ul>
<li>Cocoon 2.1 was configured at build time. This means that you have to build
Cocoon 2.1 yourself in order to get the Cocoon that you need for your
application. There was no simple upgrade path from one minor/patch release to
@@ -190,7 +198,7 @@
<li>The number of dependencies of a minimal Cocoon application (sitemaps,
pipelines, XML templates) was reduced and together they amount to less than
10MB (incl. Xalan and Xerces libs!).</li>
-</ul><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Tools</h1><ul>
+</ul><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Tools</h1><ul>
<li>The Cocoon Maven 2 plugin makes is very easy to use Cocoon together with
Maven 2 as build system. The main features are</li>
<ul>
@@ -204,9 +212,9 @@
</ul>
<li>Schema files for sitemaps.</li>
-</ul><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Deprecation</h1><ul>
+</ul><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Deprecation</h1><ul>
<li>Avalon-style component configurations</li>
-</ul><div class="fixme"><div><strong>Fixme: </strong>Deprecation is subject of an ongoing dicussion.</div></div><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Migrating 2.1 components</h1>When you have avalon based components that you want to use with the new
+</ul><div class="fixme"><div><strong>Fixme: </strong>Deprecation is subject of an ongoing dicussion.</div></div><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Migrating 2.1 components</h1>When you have avalon based components that you want to use with the new
spring configuration system make sure you are configure them right. Avalon based
components were implementing an interface to e.g. be Threadsafe. In Spring you
will need to configure the scope (default is singletone). If you see a lot of
@@ -217,7 +225,7 @@
class="org.apache.forrest.dispatcher.transformation.DispatcherTransformer">
<property name="manager" ref="org.apache.avalon.framework.service.ServiceManager"/>
</bean>
-</beans></pre><pre></pre><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Incompatible changes</h1><ul>
+</beans></pre><pre></pre><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Incompatible changes</h1><ul>
<li>All Cocoon components don't implement the Avalon Logkit logging interfaces
(<tt><a href="http://excalibur.apache.org/apidocs/org/apache/avalon/framework/logger/Logger.html">org.apache.avalon.framework.logger.Logger</a></tt>
) anymore but Commons logging instead. This change also makes it possible to
Modified: cocoon/site/site/2.2/1447_1_1.html
URL: http://svn.apache.org/viewvc/cocoon/site/site/2.2/1447_1_1.html?rev=677229&r1=677228&r2=677229&view=diff
==============================================================================
--- cocoon/site/site/2.2/1447_1_1.html (original)
+++ cocoon/site/site/2.2/1447_1_1.html Wed Jul 16 03:16:18 2008
@@ -98,6 +98,10 @@
<li >
<a href="1420_1_1.html">New in 2.2</a>
</li>
+
+ <li >
+ <a href="1454_1_1.html">Test2</a>
+ </li>
</ul>
</li>
<li>
@@ -119,6 +123,10 @@
<li >
<a href="1362_1_1.html">Deploying a Cocoon application</a>
</li>
+
+ <li >
+ <a href="1448_1_1.html">Screencasts</a>
+ </li>
</ul>
</li>
<li>
@@ -140,8 +148,8 @@
</ul>
</li>
</ul>
- <div id="contentBody"><div id="bodyText"><h1 class="docTitle">Download</h1><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Cocoon 2.2 Core</h1><p>The current version of Cocoon 2.2 can be found at our central
-<a href="../1284_1_1.html">download page</a>.</p><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Cocoon Blocks</h1><p>The download pages for each released block can be found as part of the block
+ <div id="contentBody"><div id="bodyText"><h1 class="docTitle">Download</h1><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Cocoon 2.2 Core</h1><p>The current version of Cocoon 2.2 can be found at our central
+<a href="../1284_1_1.html">download page</a>.</p><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Cocoon Blocks</h1><p>The download pages for each released block can be found as part of the block
specific documentations. In order to get an overview of what blocks are
available, use the <a href="../2.2/blocks/1204_1_1.html">list of blocks</a>.</p></div><div class="editUrl"><div><em>Errors and Improvements?</em> If you see any errors or potential improvements in this document please help
us: <a href="http://cocoon.zones.apache.org/daisy/cdocs/1447?branch=1&language=1">View, Edit or comment</a> on the latest development version (registration required).
Added: cocoon/site/site/2.2/1448_1_1.html
URL: http://svn.apache.org/viewvc/cocoon/site/site/2.2/1448_1_1.html?rev=677229&view=auto
==============================================================================
--- cocoon/site/site/2.2/1448_1_1.html (added)
+++ cocoon/site/site/2.2/1448_1_1.html Wed Jul 16 03:16:18 2008
@@ -0,0 +1,178 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<!--
+ Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements. See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership. The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied. See the License for the
+ specific language governing permissions and limitations
+ under the License.
+-->
+
+
+
+
+
+
+
+
+<html>
+ <head>
+ <title> Cocoon 2.2 Site - Screencasts
+ </title>
+ <style type="text/css" media="all">
+ @import url("./css/maven-base.css");
+ @import url("./css/maven-theme.css");
+ @import url("./css/site.css");
+ </style>
+ <link rel="stylesheet" href="./css/print.css" type="text/css" media="print" />
+ <script src="./js/getBlank.js" language="javascript" type="text/javascript"></script>
+ <meta name="author" content="The Cocoon Community" />
+ <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
+ </head>
+ <body>
+ <div id="breadtrail">
+ <p><a href="http://www.apache.org">Apache</a> » <a href="../">Cocoon</a> »</p>
+ </div>
+ <div id="top">
+ <div id="header">
+ <div class="projectlogo">
+ <a href="../"><img class="logoImage"
+ src="images/cocoon_logo.jpg"
+ alt="Apache Cocoon" border="0" /></a>
+ </div>
+ <div class="grouplogo">
+ <p class="grouptitle"><a href="../">The Apache Cocoon Project</a><img
+ src="images/apache-logo.jpg" alt="Cocoon Project Logo" /></p>
+ <form class="searchbox" action="http://www.google.com/search" method="get">
+ <input value="cocoon.apache.org" name="sitesearch" type="hidden" />
+ <input onFocus="getBlank (this, 'Search the site with google');" size="25" name="q" id="query" type="text" value="Search the site with google" />
+ <input class="searchboxsubmit" name="Search" value="Search" type="submit" />
+ </form>
+ </div>
+ </div>
+ <div id="projectBar">
+ <p class="cocoonHome"><a href="./index.html"><img
+ src="images/pmc-home.gif"
+ alt=" Cocoon 2.2
+ homepage"
+ border="0" title=" Cocoon 2.2
+ homepage" /></a></p>
+ <h1 class="projectTitle"><a href="./index.html"> Cocoon 2.2
+ </a></h1>
+ <ul class="projectList">
+ <li><strong><a href="../2.2/">Cocoon 2.2</a></em></strong></li>
+ <li><a href="../2.2/core-modules/">Core <span class="pl-version-small">2.2</span></a></li>
+ <li><a href="../2.2/blocks/">Blocks <span class="pl-version-small">2.2</span></a></li>
+ <li><a href="../2.2/maven-plugins/">Maven Plugins <span class="pl-version-small">2.2</span></a></li>
+ <li><strong><a href="../subprojects/">Subprojects</a></strong></li>
+ </ul>
+ </div>
+ <div class="projectBarClear"><!-- --></div>
+ </div>
+ <!-- end of top -->
+
+ <div id="content">
+ <ul id="menu">
+ <li>
+ Cocoon 2.2
+ <ul>
+
+ <li >
+ <a href="1327_1_1.html">Overview</a>
+ </li>
+
+ <li >
+ <a href="1447_1_1.html">Download</a>
+ </li>
+
+ <li >
+ <a href="1420_1_1.html">New in 2.2</a>
+ </li>
+
+ <li >
+ <a href="1454_1_1.html">Test2</a>
+ </li>
+ </ul>
+ </li>
+ <li>
+ Tutorials
+ <ul>
+
+ <li >
+ <a href="1159_1_1.html">Your first Cocoon application using Maven 2</a>
+ </li>
+
+ <li >
+ <a href="1290_1_1.html">Your first XML pipeline (publishing)</a>
+ </li>
+
+ <li >
+ <a href="1291_1_1.html">Modularize Cocoon apps (Using blocks)</a>
+ </li>
+
+ <li >
+ <a href="1362_1_1.html">Deploying a Cocoon application</a>
+ </li>
+
+ <li >
+ <strong>Screencasts</strong>
+ </li>
+ </ul>
+ </li>
+ <li>
+ How-Tos
+ <ul>
+
+ <li >
+ <a href="1366_1_1.html">How to configure consistent encoding in Cocoon</a>
+ </li>
+ </ul>
+ </li>
+ <li>
+ All Sitemap Components
+ <ul>
+
+ <li >
+ <a href="1347_1_1.html">All Sitemap Components</a>
+ </li>
+ </ul>
+ </li>
+ </ul>
+ <div id="contentBody"><div id="bodyText"><h1 class="docTitle">Screencasts</h1><h1 xmlns:ns="http://outerx.org/daisy/1.0" xmlns:p="http://outerx.org/daisy/1.0#publisher">Cocoon reloading class Maven plug-in - rapid development</h1><p>The following screencast how Rapid Application (Block more precisely)
+Development is achieved with <a href="../2.2/maven-plugins/maven-plugin/1.0/1295_1_1.html">Maven's RCL</a> (AKA Cocoon)
+plug-in.</p><p>Some initial steps leading to creation of a basic block are taken from
+"<a href="1159_1_1.html">Your first Cocoon application using Maven 2</a>" tutorial.
+</p><div class="note"><div><strong>Note: </strong>During the screencast old version (1.0.0-RC2) of archetype is
+being used for initial block creation. You should use always use the latest
+available version which can be checked <a href="../2.2/maven-plugins/1208_1_1.html">here</a>.</div></div><div class="includedDoc"><object Height="725" Width="1008" type="application/x-shockwave-flash" classid="clsid:D27CDB6E-AE6D-11cf-96B8-444553540000" codebase="http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=7,0,19,0"><param name="movie" value="flash/1452_1_1.swf"></param><param name="Play" value="true"></param><param name="Loop" value="false"></param><param name="Autoplay" value="false"></param><param name="Autostart" value="false"></param><embed src="flash/1452_1_1.swf" Height="725" Width="1008" Play="true" Loop="false" Autoplay="false" Autostart="false"></embed></object><br></br></div></div><div class="editUrl"><div><em>Errors and Improvements?</em> If you see any errors or potential improvements in this document please help
+ us: <a href="http://cocoon.zones.apache.org/daisy/cdocs/1448?branch=1&language=1">View, Edit or comment</a> on the latest development version (registration required).
+ </div></div></div>
+ </div>
+
+ <!-- end of content -->
+ <div id="footer">
+ <p>©
+ 1999-2008
+
+ The Apache Software Foundation
+ </p>
+ </div>
+ <script src="http://www.google-analytics.com/urchin.js" type="text/javascript">
+ </script>
+ <script type="text/javascript">
+ _uacct = "UA-1740622-3";
+ urchinTracker();
+ </script>
+
+ </body>
+</html>
\ No newline at end of file
Added: cocoon/site/site/2.2/1454_1_1.html
URL: http://svn.apache.org/viewvc/cocoon/site/site/2.2/1454_1_1.html?rev=677229&view=auto
==============================================================================
--- cocoon/site/site/2.2/1454_1_1.html (added)
+++ cocoon/site/site/2.2/1454_1_1.html Wed Jul 16 03:16:18 2008
@@ -0,0 +1,174 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<!--
+ Licensed to the Apache Software Foundation (ASF) under one
+ or more contributor license agreements. See the NOTICE file
+ distributed with this work for additional information
+ regarding copyright ownership. The ASF licenses this file
+ to you under the Apache License, Version 2.0 (the
+ "License"); you may not use this file except in compliance
+ with the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing,
+ software distributed under the License is distributed on an
+ "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ KIND, either express or implied. See the License for the
+ specific language governing permissions and limitations
+ under the License.
+-->
+
+
+
+
+
+
+
+
+<html>
+ <head>
+ <title> Cocoon 2.2 Site - Test2
+ </title>
+ <style type="text/css" media="all">
+ @import url("./css/maven-base.css");
+ @import url("./css/maven-theme.css");
+ @import url("./css/site.css");
+ </style>
+ <link rel="stylesheet" href="./css/print.css" type="text/css" media="print" />
+ <script src="./js/getBlank.js" language="javascript" type="text/javascript"></script>
+ <meta name="author" content="The Cocoon Community" />
+ <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
+ </head>
+ <body>
+ <div id="breadtrail">
+ <p><a href="http://www.apache.org">Apache</a> » <a href="../">Cocoon</a> »</p>
+ </div>
+ <div id="top">
+ <div id="header">
+ <div class="projectlogo">
+ <a href="../"><img class="logoImage"
+ src="images/cocoon_logo.jpg"
+ alt="Apache Cocoon" border="0" /></a>
+ </div>
+ <div class="grouplogo">
+ <p class="grouptitle"><a href="../">The Apache Cocoon Project</a><img
+ src="images/apache-logo.jpg" alt="Cocoon Project Logo" /></p>
+ <form class="searchbox" action="http://www.google.com/search" method="get">
+ <input value="cocoon.apache.org" name="sitesearch" type="hidden" />
+ <input onFocus="getBlank (this, 'Search the site with google');" size="25" name="q" id="query" type="text" value="Search the site with google" />
+ <input class="searchboxsubmit" name="Search" value="Search" type="submit" />
+ </form>
+ </div>
+ </div>
+ <div id="projectBar">
+ <p class="cocoonHome"><a href="./index.html"><img
+ src="images/pmc-home.gif"
+ alt=" Cocoon 2.2
+ homepage"
+ border="0" title=" Cocoon 2.2
+ homepage" /></a></p>
+ <h1 class="projectTitle"><a href="./index.html"> Cocoon 2.2
+ </a></h1>
+ <ul class="projectList">
+ <li><strong><a href="../2.2/">Cocoon 2.2</a></em></strong></li>
+ <li><a href="../2.2/core-modules/">Core <span class="pl-version-small">2.2</span></a></li>
+ <li><a href="../2.2/blocks/">Blocks <span class="pl-version-small">2.2</span></a></li>
+ <li><a href="../2.2/maven-plugins/">Maven Plugins <span class="pl-version-small">2.2</span></a></li>
+ <li><strong><a href="../subprojects/">Subprojects</a></strong></li>
+ </ul>
+ </div>
+ <div class="projectBarClear"><!-- --></div>
+ </div>
+ <!-- end of top -->
+
+ <div id="content">
+ <ul id="menu">
+ <li>
+ Cocoon 2.2
+ <ul>
+
+ <li >
+ <a href="1327_1_1.html">Overview</a>
+ </li>
+
+ <li >
+ <a href="1447_1_1.html">Download</a>
+ </li>
+
+ <li >
+ <a href="1420_1_1.html">New in 2.2</a>
+ </li>
+
+ <li >
+ <strong>Test2</strong>
+ </li>
+ </ul>
+ </li>
+ <li>
+ Tutorials
+ <ul>
+
+ <li >
+ <a href="1159_1_1.html">Your first Cocoon application using Maven 2</a>
+ </li>
+
+ <li >
+ <a href="1290_1_1.html">Your first XML pipeline (publishing)</a>
+ </li>
+
+ <li >
+ <a href="1291_1_1.html">Modularize Cocoon apps (Using blocks)</a>
+ </li>
+
+ <li >
+ <a href="1362_1_1.html">Deploying a Cocoon application</a>
+ </li>
+
+ <li >
+ <a href="1448_1_1.html">Screencasts</a>
+ </li>
+ </ul>
+ </li>
+ <li>
+ How-Tos
+ <ul>
+
+ <li >
+ <a href="1366_1_1.html">How to configure consistent encoding in Cocoon</a>
+ </li>
+ </ul>
+ </li>
+ <li>
+ All Sitemap Components
+ <ul>
+
+ <li >
+ <a href="1347_1_1.html">All Sitemap Components</a>
+ </li>
+ </ul>
+ </li>
+ </ul>
+ <div id="contentBody"><div id="bodyText"><h1 class="docTitle">Test2</h1><p>Test2</p><div class="includedDoc"><div id="contentBody"><div id="bodyText"><h1 class="docTitle">Test1</h1><p>This document has been created for testing purposes only!</p></div><div class="editUrl"><div><em>Errors and Improvements?</em> If you see any errors or potential improvements in this document please help
+ us: <a href="http://cocoon.zones.apache.org/daisy/cdocs/1454?branch=1&language=1">View, Edit or comment</a> on the latest development version (registration required).
+ </div></div></div></div></div><div class="editUrl"><div><em>Errors and Improvements?</em> If you see any errors or potential improvements in this document please help
+ us: <a href="http://cocoon.zones.apache.org/daisy/cdocs/1454?branch=1&language=1">View, Edit or comment</a> on the latest development version (registration required).
+ </div></div></div>
+ </div>
+
+ <!-- end of content -->
+ <div id="footer">
+ <p>©
+ 1999-2008
+
+ The Apache Software Foundation
+ </p>
+ </div>
+ <script src="http://www.google-analytics.com/urchin.js" type="text/javascript">
+ </script>
+ <script type="text/javascript">
+ _uacct = "UA-1740622-3";
+ urchinTracker();
+ </script>
+
+ </body>
+</html>
\ No newline at end of file
Added: cocoon/site/site/2.2/flash/1452_1_1.swf
URL: http://svn.apache.org/viewvc/cocoon/site/site/2.2/flash/1452_1_1.swf?rev=677229&view=auto
==============================================================================
Binary file - no diff available.
Propchange: cocoon/site/site/2.2/flash/1452_1_1.swf
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Modified: cocoon/site/site/2.2/license.html
URL: http://svn.apache.org/viewvc/cocoon/site/site/2.2/license.html?rev=677229&r1=677228&r2=677229&view=diff
==============================================================================
--- cocoon/site/site/2.2/license.html (original)
+++ cocoon/site/site/2.2/license.html Wed Jul 16 03:16:18 2008
@@ -97,6 +97,10 @@
<li >
<a href="1420_1_1.html">New in 2.2</a>
</li>
+
+ <li >
+ <a href="1454_1_1.html">Test2</a>
+ </li>
</ul>
</li>
<li>
@@ -118,6 +122,10 @@
<li >
<a href="1362_1_1.html">Deploying a Cocoon application</a>
</li>
+
+ <li >
+ <a href="1448_1_1.html">Screencasts</a>
+ </li>
</ul>
</li>
<li>
Modified: cocoon/site/site/2.2/project-info.html
URL: http://svn.apache.org/viewvc/cocoon/site/site/2.2/project-info.html?rev=677229&r1=677228&r2=677229&view=diff
==============================================================================
--- cocoon/site/site/2.2/project-info.html (original)
+++ cocoon/site/site/2.2/project-info.html Wed Jul 16 03:16:18 2008
@@ -97,6 +97,10 @@
<li >
<a href="1420_1_1.html">New in 2.2</a>
</li>
+
+ <li >
+ <a href="1454_1_1.html">Test2</a>
+ </li>
</ul>
</li>
<li>
@@ -118,6 +122,10 @@
<li >
<a href="1362_1_1.html">Deploying a Cocoon application</a>
</li>
+
+ <li >
+ <a href="1448_1_1.html">Screencasts</a>
+ </li>
</ul>
</li>
<li>
Modified: cocoon/site/site/2.2/team-list.html
URL: http://svn.apache.org/viewvc/cocoon/site/site/2.2/team-list.html?rev=677229&r1=677228&r2=677229&view=diff
==============================================================================
--- cocoon/site/site/2.2/team-list.html (original)
+++ cocoon/site/site/2.2/team-list.html Wed Jul 16 03:16:18 2008
@@ -97,6 +97,10 @@
<li >
<a href="1420_1_1.html">New in 2.2</a>
</li>
+
+ <li >
+ <a href="1454_1_1.html">Test2</a>
+ </li>
</ul>
</li>
<li>
@@ -118,6 +122,10 @@
<li >
<a href="1362_1_1.html">Deploying a Cocoon application</a>
</li>
+
+ <li >
+ <a href="1448_1_1.html">Screencasts</a>
+ </li>
</ul>
</li>
<li>