[ https://issues.apache.org/jira/browse/SYNAPSE-280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andreas Veithen resolved SYNAPSE-280. ------------------------------------- Resolution: Fixed The feature introduced by WSCOMMONS-461 can be used to configure Synapse to preserve CDATA sections. Added relevant documentation explaining how to set this up. > Synapse doesn't preserve CDATA sections > --------------------------------------- > > Key: SYNAPSE-280 > URL: https://issues.apache.org/jira/browse/SYNAPSE-280 > Project: Synapse > Issue Type: Bug > Components: Core > Affects Versions: NIGHTLY > Reporter: Andreas Veithen > Assignee: Andreas Veithen > Priority: Minor > Fix For: 1.3 > > > When a message is received by Synapse, any CDATA section is transformed into > a normal text node. This issue has been discussed on the mailing list, but > without getting to a conclusion: > http://www.nabble.com/Interesting-problem-introduced-by-CDATA-section-to16321118.html > A closer look reveals that the origin of the problem is that Woodstox by > default creates parsers in coalescing mode, implying that adjacent CDATA > sections and text nodes are combined and reported as a single CHARACTER > event. Therefore information about CDATA sections is lost. Note that enabling > coalescing by default is contrary to the StAX specifications and this is a > bug in the Woodstox version used by Synapse (see > http://jira.codehaus.org/browse/WSTX-140). > The problem can be solved for Synapse in standalone mode by adding the > following instruction to ServerManager#start: > StAXUtils.getXMLInputFactory().setProperty(XMLInputFactory.IS_COALESCING, > Boolean.FALSE); -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@synapse.apache.org For additional commands, e-mail: dev-h...@synapse.apache.org