Carsten Ziegeler wrote: >Christian Haul wrote: > > >>AFAIK it is possible to declare components in a sitemap using >>map:components. Thus >> >><map:components> >> <input-modules logger="core.modules.input"> >> <component-instance >>class="org.apache.cocoon.components.modules.input.DefaultsMetaModu >>le" name="my-defaults"> >> <input-module name="request"/> >> <values> >> <skin>defaultSkin</skin> >> <base-url>http://localhost:8080/cocoon</base-url> >> </values> >> </component-instance> >> </input-modules> >></map:components> >> >>would declare a new input module instance accessible with the name >>"my-defaults" for this sitemap and all subsitemaps. >> >>I haven't tested this though. But my understanding is, that this is >>supposed to work. >> >>There has been a discussion about declaring components in sitemaps a >>long time ago and I don't recall the outcome. But I believe it was >>decided not to advertise this feature since blocks are likely to >>change this. >> >> > >AFAIK, the discussion was a little bit different. Some of us wanted >to remove *all* component definitions from the sitemap, so completly >removing the <map:components> section. >But I can't recall a discussion about adding own component definitions >to the sitemap (perhaps a memory leak?). > >
I remember it, as it is a side-effect of the way the TreeProcessor handles <map:components> : this is a Configuration object used to configure a ComponentManager. So you effectively can add new components in it. >So I would strongly discourage from even trying if it works. It's >not supposed to work! > Ok, don't try it... but it works ;-) Sylvain -- Sylvain Wallez Anyware Technologies Apache Cocoon http://www.anyware-tech.com mailto:[EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
