Collapse All Expand All

.NET Framework Class Library
Members See Also

[TIBCO.EMS .NET client library 5.1 documentation]

An ObjectMessage object is used to send a message that contains a serializable object.

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

# Syntax

    [SerializableAttribute]
    public class ObjectMessage : Message,
    	ICloneable

    <SerializableAttribute> _
    Public Class ObjectMessage _
    	Inherits Message _
    	Implements ICloneable

    [SerializableAttribute]
    public ref class ObjectMessage : public Message,
    	ICloneable

# Remarks

Setting the content of a MessageObject stores a snapshot of the object. Subsequent changes to the original object do not affect the message.

.NET Compact Framework

The .NET library supports serialization for all objects. In contrast, the .NET Compact Framework library supports serialization for a restricted set of objects.

Object serialization differs among the various EMS language APIs in ways that are incompatible. An ObjectMessage contains a serialized object. Therefore EMS programs can only send an ObjectMessage to another program written in the same language; for example, Java to Java, C to C, .NET to .NET, and .NET Compact Framework to .NET Compact Framework. In particular, notice that a .NET Compact Framework client and a full .NET client cannot exchange an ObjectMessage.

Furthermore, the .NET Compact Framework supports only a limited set of objects for TheObject in an ObjectMessage—namely, bool, int, long, short, double, float, byte, bytes, char, string, short[], int[], long[], float[], double[], MapMessage, StreamMessage, and program-defined classes that implement IEMSSerialziable. Attempting to set the value to an unsupported object type results in MessageFormatException. This restriction applies only to .NET Compact Framework (the full .NET EMS API is exempt).

# Inheritance Hierarchy

System..::.Object
TIBCO.EMS..::.Message
TIBCO.EMS..::.ObjectMessage

# See Also

ObjectMessage Members
TIBCO.EMS Namespace