Preserving CDATA sections - AXIOM StAX parsing

In XML CDATA sections provide a way to tell the parser that there is no markup in the characters contained by the CDATA section. And that makes it much easier to create documents containing sections where markup characters might appear, but where no markup is intended. CDATA is commonly used for scripting language content and sample XML/HTML content.

So in context of Web Services with Apache Axis, the default settings of the AXIOM StAX parser would ignore the CDATA sections and won't preserve them after the parsing is done. In coalescing mode, the parser will not only coalescing adjacent text nodes, but also CDATA sections.
However there are cases that you need to preserve CDATA section after parsing and creating OMElement. So, in such a scenario you need to switch off the coalescing mode by setting a property in XMLInputFactory. (i.e.: "javax.xml.stream.isCoalescing" = false). The following code will create an AXIOM OMElement with preserving CDATA.





For detailed overview of Axiom please refer Andreas' Axiom User Guide.

Comentários

Postar um comentário

Postagens mais visitadas deste blog

Understanding Reactor Pattern with Java NIO

Imagem
Why non-blocking IO A typical server application, such as a web server, needs to process thousands of request concurrently. Therefore, the modern web server needs to meet the following requirements. Handling of thousands of connections simultaneously (significant number of connections may be in idle state as well) Handling high latency connections Request/response handling needs to be decoupled Minimize latency, maximize throughput and avoiding unnecessary CPU cycles Hence, to cater to such requirements, there can be several possibilities in the server application architecture. Having a pool of sockets for each client, and periodically polling them: This is the most straightforward approach; however, it is more or less impractical without non-blocking sockets. This is extremely inefficient and never scales with the increasing number of connections. Thread per socket: This is the conventional approach and was initially used in some applications and this is the only practical solution wi...
Leia mais

A new journey.. A new working place.. WSO2 Inc.

Imagem
I guess switching blogs is less riskier than switching jobs. Anyway I had to take that risk of switching jobs in last month (12/2009) as I've joined WSO2 as a Senior Software Engineer. My very first job lasted only one and half years owing to various issues I had with the type of work I got during my first employment. However it was a good experience on some rare technologies like Search Engines and Indexing.. and not forgetting C++. Now.. the context has changed.. technologies has changed.. environment has changed... So I believe it's a whole new experience to me to work for WSO2 , which is a renowned Open Source SOA Company. These are my first few steps in the world of SOA and Web Services...
Leia mais