Hi: New to the list. Been working on some XML pipeline and intermediary stuff of late and thought there might be some overlap with what Synapse is trying to do.
I was wondering if any thought has been given to allowing the use of multiple synapse.xml config files? More specifically, if you want to mediate a lot of different transmission types, then the synapse.xml file can get rather large and unweildy to maintain. Being able to use multiple config files, with some sort of selector mechanism (eg. regex, xpath, etc.) which would figure out which config file applies to a particular incoming transmission would be very useful. On a related note, is there any way to dynamically reload the config file(s) at runtime? If the config file is located on a remote server and accessed with a URL, it would be nice if there was some sort of callback that could be invoked into the Synapse server to have it reload a particular config file. This stems from some of the work I've been doing using SOA Registry/Repositories, which would be ideal for the governance and storage of the mediation configuration documents (eg. synapse.xml). My current SOAP Intermediary implementation (part of freebxml ebXML Reg/Rep OSS project) does both of the above. ...Andrzej Chaeron Corporation: Enterprise System Solutions http://www.chaeron.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
