Hiranya ... it seems that as Andreas pointed out in ws commons list, the working with Axiom in non coalescing can be a risk.
is the 'coalescing' off/on a system property ? and if not , is there any way to create a new parser instance in non coalescing mode only for synapse configuration parsing ? Thanks Indika On Fri, Apr 30, 2010 at 6:41 PM, Hiranya Jayathilaka <hiranya...@gmail.com>wrote: > Hi Folks, > > While doing some work on SYNAPSE-624, I have realized that Synapse does not > handle local entry values with CDATA elements properly. Axiom seems to drop > CDATA elements while parsing XML. For an example given the following local > entry configuration: > > <localEntry key="foo"><test><![CDATA[<SomeXML/>]]></test></localEntry> > > the serialized XML would be as follows: > > <localEntry key="foo"><test><SomeXML/></test></localEntry> > > Note that the CDATA element is gone, and its value has been partially > encoded. The way out of this issue is to disable coalescing in the parser. > But that would be globally applied to all XML parsing logic in Synapse > (unless we somehow use a separate OM builder for parsing local entries). So > how do you think we should handle this scenario? > > Thanks > -- > Hiranya Jayathilaka > Software Engineer; > WSO2 Inc.; http://wso2.org > E-mail: hira...@wso2.com; Mobile: +94 77 633 3491 > Blog: http://techfeast-hiranya.blogspot.com >
