Render XML

The Render XML activity takes an instance of an XML schema element and renders it as a stream of bytes containing XML or an XML string. The schema is processed based on the XSD file specified.

WhenTIBCO ActiveMatrix BusinessWorks generates datetime strings, it always uses UTC time. For example, the time 55 minutes, 31 seconds, and 112 milliseconds after 2PM on February 10th, 2002 would be represented as the following by the Render XML activity:

The Configuration tab has the following fields.

Field	Global Var?	Description
Name	No	The name to appear as the label for the activity in the process definition.
Description	No	Short description of the activity.
Output Style	No	Specifies whether the output should be text or binary data.
Validate Input	No	When checked, specifies that the data input to the activity should be validated against the schema specified in the Input Editor tab.
Format Using Default Namespace Prefix	No
Encoding	Yes	This field is only available when the Output Style field is set to text. This field specifies the encoding value to place into the XML header of the rendered XML data. You can specify any valid XML encoding value listed in IANA-Charsets. See http://www.iana.org/assignments/character-sets for a complete list. Encoding names are case insensitive.

The name to appear as the label for the activity in the process definition.

Description

Short description of the activity.

Output Style

Specifies whether the output should be text or binary data.

Validate Input

When checked, specifies that the data input to the activity should be validated against the schema specified in the Input Editor tab.

Format Using Default Namespace Prefix

Encoding

Yes

This field is only available when the Output Style field is set to text. This field specifies the encoding value to place into the XML header of the rendered XML data.

You can specify any valid XML encoding value listed in IANA-Charsets. See http://www.iana.org/assignments/character-sets for a complete list. Encoding names are case insensitive.

The Advanced tab allows you to specify which elements in the input schema can contain CDATA sections. CDATA sections allow you to enclose text within an element that should not be treated as XML.

The + button allows you to add elements of the input schema to the list. When you click the + button, a dialog appears that allows you to locate and select the input schema by location in the project or by namespace. Use the By Location tab if your input schema is located in the project directory. Use the By Namespace tab if you constructed the input schema on the Input Editor tab.

Use the X button to remove elements from the list and the up and down arrows to move elements in the list.

The Input Editor tab allows you to define a schema for the incoming XML data you want to render. See Appendix A, Specifying Data Schema for a complete description of using the Input Editor tab.

See TIBCO ActiveMatrix BusinessWorks Process Design for more information about mapping and transforming input data.

The input for the activity is the following.

Input Item	Datatype	Description
byteEncoding	string	This is only available when the Output Style field on the Configuration tab is set to binary. This specified the encoding value to place into the XML header in the rendered XML output. This is also the encoding used to encode the binary data. If this item is not specified, the default encoding of the Java Virtual Machine used by the process engine is used to encode the binary data. This value may not be a valid XML encoding. You can specify any valid XML encoding value listed in IANA-Charsets. See http://www.iana.org/assignments/character-sets for a complete list. Encoding names are case insensitive.
XML Schema	string	The XML schema to render. The contents of the schema are determined by the schema specified on the Input Editor tab.

This is only available when the Output Style field on the Configuration tab is set to binary.

This specified the encoding value to place into the XML header in the rendered XML output. This is also the encoding used to encode the binary data. If this item is not specified, the default encoding of the Java Virtual Machine used by the process engine is used to encode the binary data. This value may not be a valid XML encoding.

You can specify any valid XML encoding value listed in IANA-Charsets. See http://www.iana.org/assignments/character-sets for a complete list. Encoding names are case insensitive.

XML Schema

string

The XML schema to render. The contents of the schema are determined by the schema specified on the Input Editor tab.

The output for the activity is the following.

Output Item	Datatype	Description
xmlString	string	Available when text is selected in the Output Style field on the Configuration tab. This item contains the rendered XML string.
xmlBytes	bytes	Available when binary is selected in the Output Style field on the Configuration tab. This item contains a stream of bytes representing the rendered XML.

Available when text is selected in the Output Style field on the Configuration tab. This item contains the rendered XML string.

xmlBytes

bytes

Available when binary is selected in the Output Style field on the Configuration tab. This item contains a stream of bytes representing the rendered XML.

The Error Output tab lists the possible exceptions that can be thrown by this activity. See TIBCO ActiveMatrix BusinessWorks Error Codes for more information about error codes and corrective action to take.

Exception	Thrown When...
XMLRenderException	An exception occurred when rendering the data.
UnsupportedEncodingException	An unsupported encoding was specified in the byteEncoding input item. You can specify any encoding supported by Java on the system where TIBCO ActiveMatrix BusinessWorks is running.
MissingByteCountException

Exception

Thrown When...

XMLRenderException

An exception occurred when rendering the data.

UnsupportedEncodingException

An unsupported encoding was specified in the byteEncoding input item. You can specify any encoding supported by Java on the system where TIBCO ActiveMatrix BusinessWorks is running.

MissingByteCountException