Return-Path: 
 <users-return-89154-apmail-cocoon-users-archive=cocoon.apache.org@cocoon.apache.org>
Delivered-To: apmail-cocoon-users-archive@www.apache.org
Received: (qmail 20660 invoked from network); 26 Oct 2006 05:13:33 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 26 Oct 2006 05:13:33 -0000
Received: (qmail 8346 invoked by uid 500); 24 Oct 2006 08:20:21 -0000
Delivered-To: apmail-cocoon-users-archive@cocoon.apache.org
Received: (qmail 8260 invoked by uid 500); 24 Oct 2006 08:20:21 -0000
Mailing-List: contact users-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:users-help@cocoon.apache.org>
list-unsubscribe: <mailto:users-unsubscribe@cocoon.apache.org>
List-Post: <mailto:users@cocoon.apache.org>
Reply-To: users@cocoon.apache.org
List-Id: <users.cocoon.apache.org>
Delivered-To: mailing list users@cocoon.apache.org
Received: (qmail 8236 invoked by uid 99); 24 Oct 2006 08:20:20 -0000
Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 24 Oct 2006 01:20:20 -0700
X-ASF-Spam-Status: No, hits=1.4 required=10.0
	tests=SPF_NEUTRAL
X-Spam-Check-By: apache.org
Received-SPF: neutral (herse.apache.org: 128.178.50.179 is neither permitted
 nor denied by domain of patrick.refondini@pobox.com)
Received: from [128.178.50.179] (HELO psemail.epfl.ch) (128.178.50.179)
    by apache.org (qpsmtpd/0.29) with SMTP; Tue, 24 Oct 2006 01:20:09 -0700
Received: (qmail 9565 invoked from network); 24 Oct 2006 08:19:46 -0000
Received: from smartgenepc4.epfl.ch (HELO ?192.168.1.24?) (128.179.67.83)
  by psemail.epfl.ch with SMTP; 24 Oct 2006 08:19:46 -0000
Message-ID: <453DCC40.30206@pobox.com>
Date: Tue, 24 Oct 2006 10:18:08 +0200
From: Patrick Refondini <patrick.refondini@pobox.com>
User-Agent: Thunderbird 1.5.0.7 (X11/20060909)
MIME-Version: 1.0
To: users@cocoon.apache.org
Subject: Re: Cocoon 2.2  - how to wire block into webapp
References: <453CC545.4060408@pobox.com> <453D169E.9070803@otego.com>
In-Reply-To: <453D169E.9070803@otego.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Checked: Checked by ClamAV on apache.org


Hi Felix,

Felix Knecht wrote:
> HI Patrick
> 
>> Hi,
>> I have created a webapp named test and a block named demo
>>
>> They've been created using the cocoon-22-archetype-webapp and
>> cocoon-22-archetype-block
>>
>> Now I have introduce a dependency in test webapp on demo block:
>> (...)
>>   <dependencies>
>> (...)
>>     <dependency>
>>       <groupId>ch.smartgene</groupId>
>>       <artifactId>demo</artifactId>
>>       <version>1.0.0-SNAPSHOT</version>
>>     </dependency>
>>   </dependencies>
>> (...)
>>
>> I can see the demo block is deployed into the test webapp.
>>
>> My questions:
>>
>> 1. Is the above the right way to include blocks into webapp with Cocoon
>> 2.2 ?
> 
> This looks ok to me.
> You need to install the block using mvn install.
> 
>> 2. If 1. is no wrong then how can test webapp make use of what is
>> available in demo block (URL conventions /demo /blocks/demo ... to be
>> defined ?)
> 
> The url /block/demo should be the right one. You need to start the
> (web-)application first:
> - Goto the block directory and install the block (mvn install)
> - Goto to the webapp directory
> - Start the application: mvn cocoon:deploy jetty6:run (I'm not sure if
> cocoon:deploy is still needed)	
> - Point your browser to http://localhost:8888/block/demo
Yes, this is the case when I am running the demo block by itself in its 
own project.

When I run the "test" project which does include the demo block I cannot 
manage to have the same URL working.
The webapp layout I observe in test project target/cocoon-webapp 
directory is:

|-- WEB-INF
|   |-- applicationContext.xml
|   |-- cocoon
|   |   |-- cocoon.xconf
|   |   |-- lib
(...)
|   |   |   |-- demo-1.0.0-SNAPSHOT.jar
(...)
|   |   |-- spring
|   |   |   |-- cocoon-core-applicationContext.xml
|   |   |   `-- demo-application-context.xml
(...)
|   `-- web.xml
|-- blocks
|   `-- demo
|       |-- demo.js
|       |-- demo.xml
|       `-- sitemap.xmap
|-- sitemap.xmap
`-- welcome.xml

The content of the root sitemap.xmap only pipeline is as follow:
<map:pipeline>
   <map:match pattern="">
     <map:generate src="welcome.xml"/>
       <map:serialize type="xhtml"/>
     </map:match>

     <!-- ADDED FOR TEST -->
     <map:match pattern="demo">
       <map:redirect-to uri="blocks/demo/"/>
     </map:match>		

     <!-- ADDED FOR TEST -->
     <!--+
         | Mount everything else by calling the sitemap.xmap file located
	| in the requested folder (sub-folder).
	+-->
      <map:match pattern="*/**">
        <map:mount check-reload="yes" src="{1}/" uri-prefix="{1}"/>
      </map:match>
</map:pipeline>

Neither the redirect-to nor mount has the effect I expected: The demo 
block stays unreachable !

Any idea of what I overlook ?

Patrick

> 
> Port configuration can be found in test/pom.xml (test = webapp directory)
> 
>> Any hints or direction to examples, documentation are welcome.
> 
> Sample for webapp: {cocoon2.2-src}/core/cocoon-webapp
> Sample for block:  {cocoon2.2-src}/blocks
> 
> Felix
> 
>> Patrick
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
>> For additional commands, e-mail: users-help@cocoon.apache.org
>>
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
> For additional commands, e-mail: users-help@cocoon.apache.org
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org