Field Names in Messages

A TIBCO Rendezvous^® message can contain field names that are not compliant with XML naming rules. For example, XML element names can neither begin with a number, nor can they contain special characters, such as # or ^. When activities in the Rendezvous palette send or receive messages, element names in the input schemas or output schemas for the activity must comply with XML naming rules. Any element in referenced schemas in the input schemas or output schemas is automatically altered to comply with XML naming rules. From the XML-Compliant Field Names field, you can handle the incoming or outgoing messages when the field names are not valid XML names.

When the XML-Compliant Field Names field is clear, any field name in the incoming or outgoing messages not compliant with XML naming rules, is altered to comply with the rules. When this field is selected, field names in the message are left unaltered.

When publishing a message with XML-Compliant Field Names field not selected, the field names in the message sent over the transport to the receiving application are altered to comply with XML naming rules. By selecting this field, you can send the message with the original field names intact; no alterations are made to the field names. This is useful in the case where you reference a schema in the Input Editor tab that contains invalid XML names. The receiving application receives the message with the original field names, if the XML-Compliant Field Names field is not selected.

When receiving a message, not selecting the XML-Compliant Field Names field ensures that field names in the incoming message are altered to comply with XML naming rules. If the message contains fields that do not comply to XML naming rules, the output schema of the subscriber activity must specify the correct altered name to match the altered name of the field in the incoming message. Keeping the field clear leaves the field names of the message intact.