From time to time, I write development articles for other Adobe technologies (other than Adobe Experience Manager) based on community requests. This use case was made from a LiveCycle community member that I have worked with for many years.
You can create a custom LiveCycle custom service that queries a relational database, dynamically creates an XML document, and places the data within an XML document. The advantage to creating a LiveCycle service that creates XML is the XML can be developed to meet your business requirements. For this use case, assume that the requirement is the XML does not contain CDATA section.
Data within an XML document can be parsed and displayed by a client application. However, data located within an XML CDATA section cannot be parsed and is ignored. The LiveCycle custom service created in this development queries MySQL, dynamically creates an XML document, places the MySQL data within the XML document, and returns the XML. Futhermore, a .NET application invokes the service by using the web service exposed by the LiveCycle custom service.
This development article walks you through creating the custom LiveCycle custom service that returns XML data that contains data queried from MySQL. The XML does not contain additional sections such as CDATA, as shown here in a .NET client application.
In addition, this article walks you through creating the client .NET application that invokes the custom LiveCycle Service using web services. To read this development article, check back on Mon April 21, 2014.