Sylvain Wallez wrote: > > > What about using XInclude, which, through XPointer, would allow to > insert in cocoon.xconf elements from an external file that would contain > only those parts that we allow the sysadmin to change ? > > I already used this in Cocoon1 days to insert configuration values from > a central application config file inside XSP pages, and it worked like a > charm ! > I totally agree, that the cocoon.xconf is too big, no doubt.
But I hear very often complains about too many configuration files for Cocoon (web.xml, logkit.xconf, cocoon.xconf, sitemap.xmap etc). By segmenting this further, we will get a smaller cocoon.xconf, but it will not get less complicated, I fear. Using an XML editor (or a tool) for the cocoon.xconf makes the usage in my eyes much easier than splitting it into many parts. With an XML editor you can for example only display the top-level component nodes and simply select the component you want to change. So, it's still very simple. If you have several files, nearly all tools fail. And the configuration is "maintained" by Avalon, so if we decide to build a solution this should rather happend in Avalon than in Cocoon. Cheers Carsten Open Source Group sunShine - b:Integrated ================================================================ Carsten Ziegeler, S&N AG, Klingenderstrasse 5, D-33100 Paderborn www.s-und-n.de mailto: [EMAIL PROTECTED] The new weblog homepage: http://ziegeler.bei.t-online.de ================================================================ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
