|
|
Component: XML Utilities
|
|
XML utilities service to manipulate XML data.
|
Operations
|
Icon
|
Name
|
About
|
Link |
|
|
Extract SOAP Body
|
Extract SOAP body data from XML if the XML is a SOAP message, i.e. contains SOAP envelope and SOAP body.
Why use it
- We need to insert the contents of the SOAP response into an XML variable.
- We need to extract the contents of a SOAP response; to be later inserted into a PDF form.
|
Properties |
|
|
Insert XDP Envelope
|
PDF forms, always have an XDP envelope (in XML) wrapped around the form's XML data. This is called an XDP envelope. XDP envelopes are also used in the XDP form templates. This operation can add an XDP Envelope around XML data, thus making an Adobe XDP document.
Why use it
- In a render-process, you need to build some form data dynamically - using database queries etc.
- A process needs to build a PDF form template dynamically - and wrap it in an XDP envelope.
|
Properties |
|
|
Insert XML Data
|
Retrieves data from an XML document and inserts data into another XML document.
Why use it
- We need to merge some XML data together.
- We need to insert part of a Web-service response into a PDF form's data.
|
Properties |
|
|
Pretty Print
|
Adds whitespace to an XML document so that the structure is made more readable through indentation.
Why use it
- Some poorly-formatted XML needs to be made readable for presentation.
- We need to debug a generated XML document.
|
Properties |
|
|
Remove Namespaces
|
Removes namespaces (xmlns:foo="http://www.foo.com") and prefixes (foo:myData --> myData) from XML data.
Why use it
- Some XML parsers are not able to handle namespaces.
- An XML document needs to be 'de-cluttered' for presentation purposes.
|
Properties |
|
|
Remove XDP Envelope
|
PDF forms, always have an XDP envelope (in XML) wrapped around the form's XML data. This is called an XDP envelope. XDP envelopes are also used in the XDP form templates. This operation can remove the XDP Envelope wrapped around either of these.
Why use it
- An external process requires a form's data, and not it's XDP envelope.
|
Properties |
|
|
Remove XML Comments
|
Removes XML Comments from the input XML document.
Why use it
- Some XML parsers cannot handle XML comments.
- DOM navigation, and some XPath expressions, can work differently; based on the presence or abscence of XML comments.
|
Properties |
|
|
Remove XSI Type Attributes
|
Remove XSI-Type attributes from XML. Many documents that are constrained by a schema, have 'XSI:type' attributes everywhere. They reference the corresponding Schema type, are not usually necessary, and are an obstacle to making readable XML.
Why use it
- If a Web-service response contains 'xsi:type' attributes, and is used somewhere else for presentation.
- A generated XML document needs to be debugged by a developer - and the XML needs to be readable.
|
Properties |
|
|
Serialize XML into a String
|
Serialize an XML Document into a String. Most Web-service APIs require XML input/output. It generally needs to be marshalled as text/string. XML documents need to be converted to this format in order to enable inter-operation.
Why use it
- To expose a process as a Web-service and have it return textual (not object) XML.
- We need to invoke an XML operation on a remote service.
|
Properties |
|
DOWNLOADS
DOCUMENTATION
|
|
Products
LiveCycle ES Components Installer
Business Process Techniques and Patterns