Preserve a CDATA block in an XML
Recently we have been working on how to preserve a CDATA block in an XML that is circulating in a WSO2 Enterprise Service Bus.
Together with our alliance partner WSO2 we managed to put together this feature for WSO2 4.8.1 patch0514, it is a very important feature if you like to preserve a CDATA in XML and/or SOAP messages through your entire flow.
This has been an issue for one of our important client for delivering them crucial information.
However we would like to point out if you like using continuous integration such as Jenkins which is a third party component we advise you to pull the latest version that we customized in order to keep uploading and deploying your projects automatically via the CarbonUpload Service.
Note: Be sure to download the latest Jenkins Plugin that contains the customization, a pull request has been made.
WSO2 Enterprise Service Bus
WSO2 has taken a fresh look at old-style, centralized ESB architectures, and designed their unique WSO2 Enterprise Service Bus from the ground up as the highest performance, lowest footprint, and most interoperable SOA and integration middleware today. Relying on their innovative Carbon technology, the ESB delivers a smooth start-to-finish project experience that you cannot find anywhere else.
The feature rich and standards compliant WSO2 ESB delivers high performance within a lean footprint. For example, a deployed WSO2 ESB often fits within a 160 MB memory space. Don’t just take their word on performance, read how eBay uses the 100% Open Source WSO2 Enterprise Service Bus to process over 1 billion transactions per day.
Jenkins is an award-winning application that monitors executions of repeated jobs, such as building a software project or jobs run by cron. Among those things, current Jenkins focuses on the following two jobs:
• Building/testing software projects continuously, just like CruiseControl or DamageControl. In a nutshell, Jenkins provides an easy-to-use so-called continuous integration system, making it easier for developers to integrate changes to the project, and making it easier for users to obtain a fresh build. The automated, continuous build increases the productivity.
• Monitoring executions of externally-run jobs, such as cron jobs and procmail jobs, even those that are run on a remote machine. For example, with cron, all you receive is regular e-mails that capture the output, and it is up to you to look at them diligently and notice when it broke. Jenkins keeps those outputs and makes it easy for you to notice when something is wrong.