cocoon-docs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From da...@cocoon.zones.apache.org
Subject [DAISY] Updated: Modularize Cocoon apps (Using blocks)
Date Mon, 23 Jun 2008 14:51:05 GMT
A document has been updated:

http://cocoon.zones.apache.org/daisy/documentation/1291.html

Document ID: 1291
Branch: main
Language: default
Name: Modularize Cocoon apps (Using blocks) (unchanged)
Document Type: Cocoon Document (unchanged)
Updated on: 6/23/08 2:50:59 PM
Updated by: David Legg

A new version has been created, state: draft

Parts
=====

Content
-------
This part has been updated.
Mime type: text/xml (unchanged)
File name:  (unchanged)
Size: 8780 bytes (previous version: 8644 bytes)
Content diff:
(25 equal lines skipped)
    
    <p>First choose the archetype: -</p>
    
--- <pre>Choose archetype:
+++ <pre>...
+++ Choose archetype:
    1: remote -&gt; cocoon-22-archetype-block-plain (Creates an empty Cocoon block; useful
     if you want to add another block to a Cocoon application)
    2: remote -&gt; cocoon-22-archetype-block (Creates a Cocoon block containing some
small
(10 equal lines skipped)
    Define value for version:  1.0-SNAPSHOT: : <strong>1.0.0</strong>
    Define value for package: : <strong>com.mycompany.myBlock2</strong></pre>
    
--- <p>The result is a second block and you should find directory structure of your
--- application now looks as follows: -</p>
+++ <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> +-</tt><tt>myBlock1
(11 equal lines skipped)
    
    <pre>mvn install eclipse:eclipse</pre>
    
--- <p>This builds and copies the second block into your local Maven repository and
--- then creates the necessary files to allow you to import the block as a project
--- in Eclipse.</p>
+++ <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>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
+++ <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>
    
(15 equal lines skipped)
    &lt;/beans&gt;
    </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>
+++ <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>&lt;?xml version="1.0" encoding="UTF-8"?&gt;
    &lt;project&gt;
(132 equal lines skipped)


Mime
View raw message