Re: mount named blocks inconvenience

2012-05-11 Thread Jos Snellings
O yes, Francesco, that is in every way a good workaround. Thanks, Jos On Fri, May 11, 2012 at 12:43 PM, Francesco Chicchiriccò < ilgro...@apache.org> wrote: > On 10/05/2012 13:05, Jos Snellings wrote: > > Dear cocooners, > > Problem: > 1. In the definition of a named block, for: > > > This

Re: mount named blocks inconvenience

2012-05-11 Thread Francesco Chicchiriccò
On 10/05/2012 13:05, Jos Snellings wrote: Dear cocooners, Problem: 1. In the definition of a named block, for: This tells the cocoon servlet that a block "foo" is mounted on "foo" in the webapp. 2. sitemap.xmap An empty matcher like in the cocoon sample: 3. call localhost/mywebapp

mount named blocks inconvenience

2012-05-10 Thread Jos Snellings
Dear cocooners, Problem: 1. In the definition of a named block, for: This tells the cocoon servlet that a block "foo" is mounted on "foo" in the webapp. 2. sitemap.xmap An empty matcher like in the cocoon sample: 3. call localhost/mywebapp/foo or, the root of th