Udayanga, I have not studied how 'import' in existing XML based languages such as WSDL, works. But, I think the problem you pointed out may have been already solved by those languages. If so, introducing <import> construct (in multi-conf scenario) would solve the problem in a standard way. BTW, I could be wrong.
~ Indika On Fri, Mar 4, 2011 at 11:36 AM, Udayanga Wickramasinghe <[email protected]>wrote: > Hi Indika, > > On Thu, Mar 3, 2011 at 8:55 PM, indika kumara <[email protected]>wrote: > >> Udayanga, Could please show some examples that demonstrate the the problem >> in the synapse multiple xml configurations with the standard way of defining >> namespaces?. >> >> In multiple xml configurations we load synapse artifacts from different > locations. Therefore problem is, if we define namespaces in Synapse.xml > these wont be visible to other artifacts loaded from multiple locations. > ie:- namespace xmlns:m0 defined in synapse-config/synapse.xml wont be > visible to a sequence 'foo' defined in synapse-config/sequences/foo.xml > > Regards, > Udayanga-- > > *Udayanga Wickramasinghe* > Software Engineer; WSO2 Inc.; http://wso2.com, > *email: **[email protected]* <[email protected]>* cell: +94 (77) 983-4365 > blog: **http://udayangawiki.blogspot.com*<http://udayangawiki.blogspot.com/> > * > twitter: **http://twitter.com/udayanga_wick*<http://twitter.com/udayanga_wick> > * > * >
