cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Leszek Gawron <lgaw...@mobilebox.pl>
Subject Re: [2.2] Runtime deployment
Date Sat, 04 Nov 2006 11:27:08 GMT
Leszek Gawron wrote:
> 
> I am trying to fix it now.
> 

fixed. One more difference of cocoon deployer plugin vs. DeployerUtil: 
blocks are unpacked to block-name-version instead of block-name:

c:\dev\projects\XXX-pi\server\webapp\target\XXX-pi-server-webapp-1.0.0-SNAPSHOT\blocks\XXX-pi-server-piapi-1.0.0-SNAPSHOT

while it should be:
c:\dev\projects\XXX-pi\server\webapp\target\XXX-pi-server-webapp-1.0.0-SNAPSHOT\blocks\XXX-pi-server-piapi

otherwise every time you up the version number you will have to adjust 
your main sitemap.xmap:

<map:match pattern="piapi/**">
   <map:mount uri-prefix="piapi" src="blocks/XXX-pi-server-piapi/"/>
</map:match>


There's more: cocoon will not start up correctly if you leave

   <!--+
       | Include all configuration files ending with ".xconf"
       | from the xconf directory.
       +-->
   <include dir="context://WEB-INF/cocoon/avalon" pattern="*.xconf"/>

uncommented in cocoon-core.jar!/org/apache/cocoon/cocoon.xconf

The directory does not exist by default and include will fail.

-- 
Leszek Gawron                                    CTO at MobileBox Ltd.


Mime
View raw message