Re: [Proposal] Move Sources and Modules as top-level Cocoon components

[Sylvain Wallez]

Giacomo Pati wrote:

On Sat, 14 Dec 2002, Sylvain Wallez wrote:

Giacomo Pati wrote:

On Sat, 14 Dec 2002, Sylvain Wallez wrote:

<snip/>

How will blocks will give a solution ? Is it because a block contains a
xconf along with an xmap ? Will block sitemap still contain a
<map:components> ?

Yes. But the problem is IIRC only with the root sitemap, right?

This is currently a problem with the root sitemap, but actually this is
with sitemaps that don't have a parent. Blocks sitemap will fall in this
category, otherwise the vision of reusable blocks that can be downloaded
from a central repository would not be implementable.

So this problem is going to be even more present with blocks.

I don't get this.

Let's try it another way : a block has to be as independent as possible. It can have dependencies on other blocks, but the block's sitemap cannot IMO rely on a particular set of sitemap components to be declared in the root sitemap, and must therefore declare _all_ sitemap components that are used by the block.

This means that a block's sitemap will also contain a large <map:components> section, just like root sitemaps.

Therefore, with blocks, we will not only have large <map:components> in the root sitemap, but also in every block's sitemap.

Hope it's clearer ;-)

Sylvain

--
Sylvain Wallez Anyware Technologies
http://www.apache.org/~sylvain http://www.anyware-tech.com
{ XML, Java, Cocoon, OpenSource }*{ Training, Consulting, Projects }



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]