Nicola Ken Barozzi wrote: >From: "Carsten Ziegeler" <[EMAIL PROTECTED]> > >>Sylvain Wallez wrote: >> >>>Nevertheless, the treeprocessor allows to name an alternate >>>configuration file using the "config" attribute recently added by >>>Ovidiu. If you want to, we can also allow the full treeprocessor >>>configuration to be present in cocoon.xconf. >>> >>Yes, I still feel that we should remove this attribute and put >>everything in the cocoon.xconf as I want to have on single point >>of configuration for components. >> >>What do others think? >> > >I think that cocoon.xconf is becoming a bit too big to be easily managed. >
Agree. And it contains lots of configuration items that the average user should not have to change. A lot of components have default configurations hard-coded in their source files. For the treeprocessor, having this default written in Java code would be a PITA, hence the "treeprocessor-builtins.xml" file. I'm going to update TreeProcessor.configure() so it is more consitent with the usual behaviour : if a configuration is given in cocoon.xconf, use it, else use the defaults defined by treeprocessor-builtins.xml. But I still want the possibility of naming a separate config file (see also below). >IMHO it should get separated in different config files, and to prevent >single Components to devise their own Configuration scheme, there should be >a standard way of doing it. > >Maybe a mount-config element or a standard config="" attribute could do the >trick. > I like this. 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 ! 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]
