I forgot to mention this, but if people like this idea I'd be willing to be the one to actually have to try to make it happen.
Also, I'd like to point out the way I've envisioned/described it would be backwards compatible with the current setup and a blank base configuration. The case of cocoon.xconf would be to just increase the search path for configuration to both files, so having all the configuration in the local file shouldn't be a problem, and having all the components configured in the local file also wouldn't be a problem (the base cocoon.xconf could even just be detected as "not there" and ignored, and the base sitemap could just not be specified in cocoon.xconf and therefor not looked for). The last thing is maybe there's some obvious way to actually do this seperation of configuration now and I just never knew about it.... in which case, anyone mind letting me in on the secret? :) Please? hehe Sincerely, Jay Freeman (saurik) [EMAIL PROTECTED] ----- Original Message ----- From: "Jay Freeman (saurik)" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Saturday, August 16, 2003 5:58 PM Subject: Config File Proposal (was... sort of...: [ANN] Apache Cocoon 2.1 Released - binary??) ... > What I would want is for each current configuration file to get split in 2, > one for base configuration, one for local configuration. For the sitemap, > the pipelines go in the latter (although error handlers can be defined in > the prior one and overridden in the latter), and components can go in either > (the configurations here are merged, although names from the latter override > names from the former). Similar process for cocoon.xconf. All the > configuration of how XSP works stays in the base configuration, buy my > single jdbc datasource configuration entry goes in the local one. > ... > > Sincerely, > Jay Freeman (saurik) > [EMAIL PROTECTED]
