Hi Ruwan, I’m also +1 on this one. I hope it will still be possible to move the whole synapse-config directory out of the directory structure to any place the user wants it to have like it is now possible for synapse.xml.
Regards, Eric ________________________________ From: Ruwan Linton [mailto:[email protected]] Sent: Monday, August 10, 2009 7:47 AM To: [email protected] Subject: [PROPOSAL] Hierarchical directory based configuration as the default configuration Folks, yet another proposal :-) Shall we make the hierarchical directory based synapse configuration to be the default configuration mechanism? It will give Synapse many advantages while we can make it have no disadvantages by supporting a synapse.xml file inside the root of the configuration hierarchy. So what I am proposing is that we create the repository/conf/synapse-config/ directory by the build and treat that as the synapse configuration root which will have sup directories to hold individual artifacts like sequences, endpoints and so on. At the same time we should support a synapse.xml file to be embeded with multiple elements in the configuration root (in this case the direcotry "synapse-config") supporting the existing behaviour. With this we can get rid of the registry.xml and the local-entries.xml files that we have on the configuration root and bring them into the synapse.xml itself. This would make the configuration nicely placed with different levels as well as supporting the flat file at the same time by default. WDYT?
