[DAISY] Updated: BD: Tutorial: Using the block deployer to create a Cocoon web application

[daisy]

A document has been updated:

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

Document ID: 797
Branch: main
Language: default
Name: BD: Tutorial: Using the block deployer to create a Cocoon web application 
(unchanged)
Document Type: Cocoon Document (unchanged)
Updated on: 1/11/06 10:13:57 PM
Updated by: Reinhard Pötz

A new version has been created, state: publish

Parts
=====
Content
-------
This part has been updated.
Mime type: text/xml (unchanged)
File name:  (unchanged)
Size: 10759 bytes (previous version: 10636 bytes)
Content diff:
(116 equal lines skipped)
    an XML schema file that describes the structure. The Maven archetype already
    provides following descriptor:</p>
    
--- <pre>&lt;deploy xmlns=""&gt;
---    &lt;cocoon version="2.2.0"/&gt;
+++ <pre>&lt;deploy xmlns="http://apache.org/cocoon/blocks/deploy/1.0"&gt;
       &lt;block id="core" urn="org.apache.cocoon:cocoon-core:2.2.0"/&gt;
    &lt;/deploy&gt;</pre>
    
--- <p class="fixme">Explain the content;<br/>
--- It's hasn't been defined yet, how a Cocoon 2.2 webapp looks like. IMO it is 
a
--- web.xml pointing to a servlet and a couple of blocks deployed to 
/WEB-INF/blocks
--- </p>
+++ <p class="fixme">It's hasn't been defined yet, how a Cocoon 2.2 webapp looks
+++ like. IMO it is a web.xml pointing to a servlet and a couple of blocks 
deployed
+++ to /WEB-INF/blocks. No special core.</p>
    
    <h2>Install a simple block (minimal configuration)</h2>
    
    <p>Now we start to add the block from the former tutorial:</p>
    
--- <pre>&lt;deploy xmlns=""&gt;
+++ <pre>&lt;deploy xmlns="http://apache.org/cocoon/blocks/deploy/1.0"&gt;
      ...
      &lt;block id="my-block" urn="com.mycompany:myBlock:1.0"/&gt;
      ...
(6 equal lines skipped)
    <p>If you block contains a sitemap, you can mount it in your web 
applications
    URI space.</p>
    
--- <pre>&lt;deploy xmlns=""&gt;
+++ <pre>&lt;deploy xmlns="http://apache.org/cocoon/blocks/deploy/1.0"&gt;
      ...
      &lt;block id="myBlock" urn="com.mycompany:myBlock:1.0"&gt;
        &lt;mount path="/myBlock"/&gt;
(9 equal lines skipped)
    and updates ./target/[project-name]/WEB-INF/wiring.xml. You can override the
    target directory the deployer's target directory in deploy.xml</p>
    
--- <pre>&lt;deploy xmlns=""&gt;
+++ <pre>&lt;deploy xmlns="http://apache.org/cocoon/blocks/deploy/1.0"&gt;
      &lt;cocoon version="2.2" <strong>url="/opt/my-webapp"</strong>/&gt;
      ...
    &lt;/deploy&gt;</pre>
(42 equal lines skipped)
    
    <p>you can set the properties for foo1 and foo2 or use the default 
values.</p>
    
--- <pre>&lt;deploy  xmlns="http://apache.org/cocoon/blocks/deploy/1.0"&gt;
+++ <pre>&lt;deploy xmlns="http://apache.org/cocoon/blocks/deploy/1.0"&gt;
      &lt;properties&gt;
        &lt;property name="foo1" value="xyz"/&gt;
      &lt;/properties&gt;   
(144 equal lines skipped)


Fields
======
no changes

Links
=====
no changes

Custom Fields
=============
no changes

Collections
===========
no changes