Daniel Fagerstrom wrote:
> What I propose is that the block descriptor block.xml contains both a
> sitemap path (as it has today) and a component configuration path(s) (a
> new addition) both optional. Then a block with a component configuration
> path will create a root component manager where everything from the
> component configuration is exported. If there also is a sitemap path,
> the sitemap processor will use the root component manager as parent
> component manager. If there is a sitemap configuration path but no
> component configuration path the block will not export any components.
>
> I prefer the described solution partly because a sitemap configuration
> IMO not make sense for component only blocks and partly because it
> provide a very smooth evolutionary path towards real blocks. The blocks
> can look like today, only a block.xml with paths to the current
> component configuration pat, main sitemap etc and a Manifest.mf is needed.
Ok, sounds good.
Vadim
|