Collapse All Expand All

.NET Framework Class Library
Members See Also

[TIBCO.EMS.UFOCLIENT .NET client library 5.1 documentation]

Messages carry information among EMS client programs.

The Message interface is the root interface of all TIBCO Enterprise Message Service .NET messages. It defines the message header and the acknowledge method used for all messages. All other message types extend this root interface.

Namespace: TIBCO.EMS.UFO
Assembly: TIBCO.EMS.UFO (in TIBCO.EMS.UFO.dll)

# Syntax

    [SerializableAttribute]
    public class Message : ICloneable

    <SerializableAttribute> _
    Public Class Message _
    	Implements ICloneable

    [SerializableAttribute]
    public ref class Message : ICloneable

# Remarks

The TIBCO Enterprise Message Service .NET Client API messages are composed of the following parts:

- Header - Headers associate a fixed set of header field names with values. Clients and providers use headers to identify and route messages. All messages support the same set of header fields.
- Properties - Each message contains a built-in facility for supporting application-defined property values. Properties associate an extensible set of property names with values. The EMS server uses properties to attach ancillary information to messages. Client applications can also use properties—for example, to customize message filtering.
- Body - The body of a message bears the information content of an application. Several types of message body organize that information in different ways.

Message Bodies

The TIBCO EMS .NET API defines five types of message body:

- Stream - A StreamMessage object's message body contains a stream of primitive values in the .NET programming language (".NET primitives"). It is filled and read sequentially.
- Map - A MapMessage object's message body contains a set of name-value pairs, where names are String objects, and values are .NET primitives. The entries can be accessed sequentially or randomly by name. The order of the entries is undefined.
- Text - A TextMessage object's message body contains a .NET String object. This message type can be used to transport plain-text messages, and XML messages.
- Object - An ObjectMessage object's message body contains a Serializable .NET object.
- Bytes - A BytesMessage object's message body contains a stream of uninterpreted bytes. This message type is for literally encoding a body to match an existing message format. In many cases, it is possible to use one of the other body types, which are easier to use. Although the TIBCO EMS .NET API allows the use of message properties with byte messages, they are typically not used, since the inclusion of properties may affect the format.

JMS Headers as .NET Properties

These JMS headers are available as .NET properties of message objects:

- CorrelationID
- CorrelationIDAsBytes
- DeliveryMode
- MsgDeliveryMode
- Destination
- Expiration
- MessageID
- MsgType
- Priority
- Redelivered
- ReplyTo
- Timestamp

# Inheritance Hierarchy

System..::.Object
TIBCO.EMS.UFO..::.Message
TIBCO.EMS.UFO..::.BytesMessage
TIBCO.EMS.UFO..::.MapMessage
TIBCO.EMS.UFO..::.ObjectMessage
TIBCO.EMS.UFO..::.StreamMessage
TIBCO.EMS.UFO..::.TextMessage

# See Also

Message Members
TIBCO.EMS.UFO Namespace