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/06/28 21:21:41 UTC
svn commit: r672575 - in /cocoon/site/site/2.2: 1159_1_1.html 1291_1_1.html
1362_1_1.html
Author: gkossakowski
Date: Sat Jun 28 12:21:39 2008
New Revision: 672575
URL: http://svn.apache.org/viewvc?rev=672575&view=rev
Log:
Publish updated tutorials. Thanks to David Legg for his effort of updating these docs.
Modified:
cocoon/site/site/2.2/1159_1_1.html
cocoon/site/site/2.2/1291_1_1.html
cocoon/site/site/2.2/1362_1_1.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=672575&r1=672574&r2=672575&view=diff
==============================================================================
--- cocoon/site/site/2.2/1159_1_1.html (original)
+++ cocoon/site/site/2.2/1159_1_1.html Sat Jun 28 12:21:39 2008
@@ -119,6 +119,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,29 +146,48 @@
</ul>
<div id="contentBody"><div id="bodyText"><h1 class="docTitle">Your first Cocoon application using Maven 2</h1><p>In this tutorial, you will:</p><ol type="1">
<li>Create a Cocoon block (the application resources and logic)</li>
-<li>Import the block as project in Eclipse</li>
-<li>Start the block as web application and access it from your browser</li>
-</ol><h1 xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">Creating a block</h1><div class="note"><div><strong>Note: </strong>First, make sure that you have Maven 2.0.6 or above installed.
-You can check this by calling mvn --version from command line. If this doesn't
-work for you, read the
+<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
+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>Create a new directory which will be the root directory of your Cocoon
-application. For this tutorial, let's name it <tt>getting-started-app</tt>.The next step is creating a Cocoon block which will contain your custom
-application. The development of any Cocoon web application should be done within
-a block. Again, for this purpose there is a Maven archetype:<pre>mvn archetype:create
- -DarchetypeGroupId=org.apache.cocoon
- -DarchetypeArtifactId=cocoon-22-archetype-block
- -DarchetypeVersion=1.0.0
- -DgroupId=com.mycompany
- -DartifactId=myBlock1
-</pre><div class="note"><div><strong>Note: </strong>Once again for copy and paste without line feeds:<br xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0"></br>
-<tt xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">mvn archetype:create -DarchetypeGroupId=org.apache.cocoon
--DarchetypeArtifactId=cocoon-22-archetype-block -DarchetypeVersion=1.0.0
--DgroupId=com.mycompany -DartifactId=myBlock1</tt></div></div><div class="note"><div><strong>Note: </strong>If you are using a cocoon binary build from svn trunk then you
+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
+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
+blocks. Cocoon blocks are little different to other Maven blocks except they
+have a particular expected <a href="../2.2/core-modules/core/2.2/1263_1_1.html">directory and file
+structure</a>.<div class="note"><div><strong>Note: </strong>You could manually create your blocks, but a simpler and less
+error-prone process is to use Maven's 'archetype' plugin. This allows you to
+select from a list of block types and have Maven create them for you. By
+default, the list of Maven archetypes is quite large. For convenience, a
+catalog of Cocoon specific archetypes is available on the Cocoon web site and
+you will make use of this in the following instructions.</div></div>Run the following Maven command:<pre>mvn archetype:generate -DarchetypeCatalog=http://cocoon.apache.org
+</pre><p>Maven will generate some output and then interactively ask you for some
+information:</p><pre>Choose archetype:
+1: remote -> cocoon-22-archetype-block-plain (Creates an empty Cocoon block; useful
+ if you want to add another block to a Cocoon application)
+2: remote -> cocoon-22-archetype-block (Creates a Cocoon block containing some small
+ 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><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>
+</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
+from all others. It is also the name of the directory that will be created to
+contain the block's files. The package is the Java package that any Java files
+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>)
-</div></div>Looking at the filesystem, you should find following directory structure:<pre>getting-started-app
+</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
+-pom.xml
+-src
@@ -174,49 +197,46 @@
Eclipse manually.<br xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0"></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 - General -
-Existing Projects</em>.</p><p>If that's the first time you use Eclipse together with a project created by
-Maven 2, we recomment to read the
+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 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 all necessary configurations.
-</p><p>You can then run</p><pre>mvn jetty:run</pre><p>and point your browser at <tt>http://localhost:8888/myBlock1/</tt> and get a
+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
+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
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><p>This process can be manually triggered with <tt>mvn cocoon:prepare</tt> too.
-</p><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 block. You have also been able to run the block in
-Jetty. Of course, that was only the first step in order to get a "Hello world"
-as result. If you wonder how you can do some useful stuff like writing your own
-Cocoon pipeline or some Java code, there are more tutorials:</p><ul>
+</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.
+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>
-Cocoon has become famous for XML pipelines. At this tutorial you will learn how
-to setup your first pipeline and will learn the most important things about
-Cocoon sitemaps.</li>
+Cocoon is well known for its XML pipelines. In this tutorial you will learn how
+to setup your first pipeline and discover the power of Cocoon sitemaps.</li>
<li><a href="1291_1_1.html">Adding a second block</a><br></br>
-While following this tutorial, you will create a web application that has a
-dependency on one block. There are use cases that require more than one block,
-e.g. you want to have all style specific resources within a single block that
-can be easily exchanged at deployment time (aka skinning).</li>
+This tutorial creates a web application that has a dependency on another block.
+There are use cases that require more than one block, e.g. you want to have all
+style specific resources within a single block that can be easily exchanged at
+deployment time (aka skinning).</li>
<li><a href="../2.2/maven-plugins/maven-plugin/1.0/1297_1_1.html">Usage of the reloading classloader plugin</a><br></br>
The reloading classloader plugin enables rapid development of Cocoon
applications since you don't have to restart the servlet container whenever one
-of your Java classes changes. Additionally it provides all settings to enable
-the reload of Cocoon resources too.</li>
+of your Java classes changes. Additionally, it enables the reloading of Cocoon
+resources too if they change.</li>
<li><a href="1362_1_1.html">Deploying a Cocoon application<br></br>
-</a>Although you have already been able to run this block, you most probably
-need a Java web application (war file) in order to deploy it to the servlet
-container (Tomcat, Jetty, etc.) of your choice.<a href="../2.2/core-modules/core/2.2/1263_1_1.html"><br></br>
+</a>Eventually, you will probably need to create a Java web application (war
+file) in order to deploy your application to a servlet container such as Tomcat
+or Jetty, etc. This tutorial shows you how.<a href="../2.2/core-modules/core/2.2/1263_1_1.html"><br></br>
</a></li>
-</ul>For the time being, we <em>recommend</em> the usage of <em>Maven 2</em> as
+</ul>For the time being, we <em>recommend</em> you use <em>Maven 2</em> as your
build system (though there is no hard dependency on it). This has the advantage
that the build system is standardized and Cocoon web applications can reuse the
-toolset (create Eclipse configuration files, release, produce documentation,
-etc.) that Maven offers. More information about Maven 2 can be found at the
-project <a href="http://maven.apache.org">website</a>. Especially we recommend
-reading<ul>
+toolset (create Eclipse configuration files, create releases, produce
+documentation, etc.). More information about Maven 2 can be found at the project
+<a href="http://maven.apache.org">website</a>. We especially recommend reading:
+<ul>
<li>
<a href="http://maven.apache.org/guides/getting-started/maven-in-five-minutes.html">Maven
in 5 minutes</a> and the</li>
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=672575&r1=672574&r2=672575&view=diff
==============================================================================
--- cocoon/site/site/2.2/1291_1_1.html (original)
+++ cocoon/site/site/2.2/1291_1_1.html Sat Jun 28 12:21:39 2008
@@ -119,6 +119,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>
@@ -150,13 +154,20 @@
<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
-the Maven 2 archetype again:<pre>mvn archetype:create
- -DarchetypeGroupId=org.apache.cocoon
- -DarchetypeArtifactId=cocoon-22-archetype-block
- -DarchetypeVersion=1.0.0
- -DgroupId=com.mycompany
- -DartifactId=<strong xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">myBlock2</strong> </pre>The result is a second block and you should find following directory
-structure:<pre>getting-started-app
+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
+ if you want to add another block to a Cocoon application)
+2: remote -> cocoon-22-archetype-block (Creates a Cocoon block containing some small
+ 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
+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
| +-pom.xml
| +-src
@@ -166,10 +177,11 @@
+-src
+-[...]
-</tt></pre>Then run<pre>mvn install eclipse:eclipse</pre><p>in order to make it ready for be imported in Eclipse and to put it into the
-local Maven repository. Then you can import the project into 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>block2</tt> from
-within <tt>block1</tt>. You have to establish the connection between the two
-blocks. Edit
+</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>
+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>
</p><pre><?xml version="1.0" encoding="UTF-8"?>
<beans xmlns="http://www.springframework.org/schema/beans"
@@ -187,8 +199,9 @@
</bean>
</beans>
-</pre><p>Additionally add the new block as dependency to the block's Maven project
-descriptor (<tt>getting-started-app/<strong>myBlock1</strong>/pom.xml</tt>):</p><pre><?xml version="1.0" encoding="UTF-8"?>
+</pre><p>Additionally, you have to record the fact that myBlock1 has a dependency on
+myBlock2 by editing myBlock1's Maven project descriptor
+(<tt>getting-started-app/<strong>myBlock1</strong>/pom.xml</tt>):</p><pre><?xml version="1.0" encoding="UTF-8"?>
<project>
[...]
<dependencies>
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=672575&r1=672574&r2=672575&view=diff
==============================================================================
--- cocoon/site/site/2.2/1362_1_1.html (original)
+++ cocoon/site/site/2.2/1362_1_1.html Sat Jun 28 12:21:39 2008
@@ -119,6 +119,10 @@
<li >
<strong>Deploying a Cocoon application</strong>
</li>
+
+ <li >
+ <a href="1448_1_1.html">Screencasts</a>
+ </li>
</ul>
</li>
<li>
@@ -153,17 +157,23 @@
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>Change into it and invoke the <tt>cocoon-22-archetype-webapp</tt> archetype:
-<pre>mvn archetype:create
- -DarchetypeGroupId=org.apache.cocoon
- -DarchetypeArtifactId=cocoon-22-archetype-webapp
- -DarchetypeVersion=1.0.0
- -DgroupId=com.mycompany
- -DartifactId=<tt xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">myCocoonWebapp</tt>
-</pre><div class="note"><div><strong>Note: </strong>For copy and paste without line feeds:<br xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0"></br>
-<tt xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">mvn archetype:create -DarchetypeGroupId=org.apache.cocoon
--DarchetypeArtifactId=cocoon-22-archetype-webapp -DarchetypeVersion=1.0.0
--DgroupId=com.mycompany -DartifactId=</tt><tt xmlns:p="http://outerx.org/daisy/1.0#publisher" xmlns:ns="http://outerx.org/daisy/1.0">myCocoonWebapp</tt></div></div>Looking at the filesystem, you should find following directory structure:<pre>getting-started-app
+</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
+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
+</pre>Choose the web application archetype:<pre>Choose archetype:
+1: remote -> cocoon-22-archetype-block-plain (Creates an empty Cocoon block; useful
+ if you want to add another block to a Cocoon application)
+2: remote -> cocoon-22-archetype-block (Creates a Cocoon block containing some small
+ 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>
+</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
| +-pom.xml
| +-src
@@ -176,9 +186,9 @@
+-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>In order to use blocks as dependencies you need to <em>install</em> them into
+</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
Maven's local repository. First go to <tt>myBlock1/</tt> directory and execute
-following command:<pre>mvn install
+following command:</p><pre>mvn install
</pre><p>Then go to <tt>myBlock2/</tt> and execute the same command. This way both
blocks will get installed into local repository where Maven stores all artifacts
that can be used as dependencies.</p><p>So far the web application <tt>myCocoonWebapp</tt> doesn't have any
@@ -243,12 +253,12 @@
</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
that instead of using (for example) the URI
-<tt>http://localhost:8888/myBlock/foo/bar</tt> to request a page, you would
+<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>myBlock/src/main/resources/META-INF/cocoon/spring/blockServlet.xml </tt>,
+<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 <tt>mvn:install</tt>.</p></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: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
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>