cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Leszek Gawron <lgaw...@mobilebox.pl>
Subject Re: My first steps with cocoon 2.2 mavenized application
Date Wed, 02 Aug 2006 07:26:51 GMT
Reinhard Poetz wrote:
> Leszek Gawron wrote:
>> Reinhard Poetz wrote:
>>>> Does that mean that even simplest application needs 2 maven modules?
>>>
>>> not necessarily but it is recommended (IMO). If you put all your code 
>>> into the /src/main/java and /src/main/webapp directories it should 
>>> work too.
>>
>> Apart from the fact that some paths are hardcoded. Like in sitemap:
>>
>> <map:match pattern="blocks/myBlock/**">
>>  <map:mount uri-prefix="blocks/myBlock"
>>     src="file:/C:/temp/xxx/myBlock/src/main/resources/COB-INF/"/>
>> </map:match>
> 
> when you call "cocoon:deploy" on a block (jar artifact), a minimal 
> webapp is created which uses hard-coded absolute paths. I don't see a 
> problem with this as it's only useful at development time.
> 
>> So I can happily do some development but not release.
> 
> yes, that was my intention.
> 
>> Is there any way now to change the block mount point (without editing 
>> sitemaps manually of course)? Is there a way to make one block the 
>> default one and mount it under "/"?
> 
> The current behaviour is that when you call "/", you are redirected to 
> the default one. Is that not enough?

For development purposes of a single block - probably enough.

-- 
Leszek Gawron                                      lgawron@mobilebox.pl
IT Manager                                         MobileBox sp. z o.o.
+48 (61) 855 06 67                              http://www.mobilebox.pl
mobile: +48 (501) 720 812                       fax: +48 (61) 853 29 65

Mime
View raw message