And, also In the multiple XML configurations, do we use the 'import' in the synapse XML - import sequence definitions, proxy definitions, etc.? The Use of 'import' construct prevails in almost every language.
~ Indika On Thu, Mar 3, 2011 at 9:25 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?. > > Personally, I would prepare for a standard method if it does not make a > negative impact on Usability. As the synapse language is based on XML, we > may expect the users having good knowledge about the XML related > technologies (XML, XPath, XSLT, etc) may find it is easy to understand and > memorize the language by intuition. > > Thanks, > > Indika > > > On Wed, Mar 2, 2011 at 3:50 PM, Udayanga Wickramasinghe <[email protected] > > wrote: > >> Hi, >> >> On Tue, Mar 1, 2011 at 8:31 PM, Andreas Veithen < >> [email protected]> wrote: >> >>> You can already achieve that in a standard way by adding >>> xmlns:m0="http://org.sample.services"; to the _root_ element of the >>> synapse.xml file. Why would one want to introduce a non standard way >>> of doing things? >>> >> >> yes true..but we have a problem to use this strategy in synapse multiple >> xml configurations.. >> >> Regards, >> Udayanga >> >> >>> >>> Andreas >>> >>> On Tue, Mar 1, 2011 at 11:51, Udayanga Wickramasinghe <[email protected]> >>> wrote: >>> > Hi devs, >>> > Currently synapse expressions (expression="xpath" OR value={xpath} ) >>> with >>> > xpath needs to have namespaces declared within the element. We think it >>> is >>> > better to include namespaces construct at synapse.xml that any xpath >>> > construct would be able to refer to .For example we can define ; >>> > <namespaces> >>> > <namespace name="m0">http://org.sample.services</namespace> >>> > <namespace name="m1">http://org.sample.services</namespace> >>> > ....... >>> > .... >>> > </namespaces> >>> > >>> > This way any expression can correspond to declared a namespace without >>> > actually defining them in their local element; >>> > ie:- >>> > >>> > <callout serviceURL="https://api.sample.enp/2.0";> >>> > <source xpath="m0:Body/child::*[fn:position()=1] | >>> > m1:Body/child::*[fn:position()=1]" /> >>> > <target key="key" /> >>> > </callout> >>> > >>> > IMO this implementation will greatly improve readability of the >>> > configuration. WDYT? >>> > >>> > Regards, >>> > Udayanga >>> > >>> > -- >>> > Udayanga Wickramasinghe >>> > Software Engineer; WSO2 Inc.; http://wso2.com, >>> > email: [email protected] cell: +94 (77) 983-4365 >>> > blog: http://udayangawiki.blogspot.com >>> > twitter: http://twitter.com/udayanga_wick >>> > >>> > >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: [email protected] >>> For additional commands, e-mail: [email protected] >>> >>> >> >> >> -- >> *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> >> * >> * >> > >
