> From: kingadziembowska [mailto:[EMAIL PROTECTED]] > > I have to admitt that now I am tottaly confused! > Until today i was under impression that all Avalon components observed in > Cacoon framework belongs to one of two categories: > 1. Those explicitely used in the pipeline definitions. > 2. Those which are not. > Then the components from the 1. category were registered in the sitemap. > The components from the second category were registered in the cocoon.xconf. > > Today during first half day, learned that the components from the first > category can be registered in cocoon.xconf. > It was looking that they are 100% this same. > In the second half day I learned that sitemap components registered in > cocoon.xconf are 50% of components registersd in the sitemap. How can it > work???? > > Then I do not grasp this picture! > I need explanations!
Here it is. 1. Any component can be declared in the cocoon.xconf 2. Only some components can be declared in the sitemap because of the limited sitemap syntax. 3. Any direct component (serializer/generator/transformer) and SAX connector implements SitemapModelComponent and setup method is called on it by the pipeline. See AbstractEventPipeline, setupPipeline method. 4. All other sitemap components (actions/selectors/etc) simply do not have setup method, so there is no issue. 5. All other components not covered in (4) and (5) even if they implement SitemapModelComponent won't have setup method called, unless I'm mistaken. Hope now it is clear. PS: This point number 5... Is it a bug or feature? Vadim > Kinga --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
