RISE to Bloome Software
Log In    
Home
RISE
Marshal
Download
 
 
Site Map Site Map
Link to Us Link to Us
r2bsoftware.se r2bsoftware.se
 
 
RISE Version 4.5RISE Version 4.5
RISE Visual ModelingRISE Visual Modeling
AJAX Code GeneratorAJAX Code Generator
 
 
Bookmark and Share
 
Click to hide navigation tree

Embed Xml Data Processor

The Embed Xml data processor allows you to embed harvested xml as part of your export file. While this gives you a very flexible way of embedding harvested Xml, there is of course also a risk of embedding corrupt xml. Make sure that the harvested xml is valid. The data processor attempts to validate the harvested xml, and will throw an exception if invalid xml is detected.

If you embed using mode DocumentInner, see below, make sure that the embedded nodes do not rely on namespaces defined at the root node of the harvested xml document. If such a dependency exist, you must manually define these namespaces in the marshal tree, probably in the namespace manager of the parent query node or the root node.

Since Marshal does not have any knowledge of the xml that is embedded at runtime, you will not be able to generate a complete Xsd for your model using Marshal. If you need an Xsd, you may generate an Xsd and complete it with a definition of the embedded nodes.


Embed Xml data processor properties

Data processor
Name The name of the data processor currently in use by the selected leaf. To change data processor, select the name property and click on the ellipsis button. Select the appropriate data processor in the form that is displayed.
Settings
Mode The Embed Xml dataprocessor validates the harvested xml before inserting it into the export file. Select the mode appropriate for you application.
Document: The harvested xml is a valid xml document. The root node of the harvested xml document is inserted into the export file.
DocumentInner: The harvested xml is a valid xml document. The sub elements of the root node are inserted into the export file.
Fragment: The harvested xml is a fragment, i.e. not a complete xml document. The entire harvested xml fragment is inserted into the export file.