cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From giacomo <giac...@apache.org>
Subject Re: Commentary (was Re: [Analysis] Cocoon, The Play)
Date Sat, 13 Apr 2002 17:11:53 GMT
On Sat, 13 Apr 2002, Ovidiu Predescu wrote:

> On Sat, 13 Apr 2002 14:06:53 +0200 (CEST), giacomo <giacomo@apache.org> wrote:
>
> > For the exported components of the deployed Cocoon Blocks I see two
> > ways of making them available to the other Cocoon Blocks:
> >
> >  1) Have a root CM populated with the exported components from each
> > Cocoon Block.
> >
> >  2) Populate the CM for each Cocoon Block with components the Cocoon
> > Block in question depoends on.
> >
> > In 1) we choose a lazy way of collection all available components into
> > one CM. The approach in 2) makes access to components possible exactly
> > as mentioned in the CBD for the block.
>
> How do we make sure that blocks that need conflicting versions of the
> same block still work fine? If a block populates the root CM with its
> dependency classes, the next block coming along will mess up with
> them. Perhaps a tree like structure for CM's will help here, where the
> root CM is protected from writing to.

Oops, you got me :). Yes, versioning of blocks make approach 1)
unsuitable. Approach 2) will do the trick. Each blocks CM gets populated
with the blocks it depends on.

Giacomo


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


Mime
View raw message