I'll respond to everything else a little bit later--I need a little time to digest all the information.
> From: Stephen McConnell [mailto:[EMAIL PROTECTED]] > > Ok - I've bitten the bullet and downloaded the Cocoon source > distribution and I'm now looking at AbstractSitemap. First > impressions > are that there is a lot that can be moved into meta-info service > dependencies. Second impression - the sitemap smells and feels like a > container (needs meta-data to function). But that's after 10 mins. Excellent. The Sitemap is a special type of container that also handles a portion of the processing (i.e. setting up the pipelines). In fact, Cocoon has a "hierarchical" container infrastructure. At its core is the Cocoon object (the root container) that mounts the root sitemap. The root container holds all the generic components that are shared throughout the rest of the system. Each sitemap and subsitemap has a set of processing components that are associated with it. A child sitemap can override a mapping that is defined in a parent sitemap--and that mapping's scope is limited to the child sitemap and its children. That is the "big picture". The problem is the container implementations. They currently use ECM, combined with the Sitemap (which used to be compiled at runtime making its use troublesome). The two together act as one container (even though the ECM is the part that holds the components). Each Sitemap has its own associated ECM. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
