javax.jms: public interface: ObjectMessage

javax.jms
public interface: ObjectMessage [javadoc | source]

All Implemented Interfaces:
Message

An ObjectMessage object is used to send a message that contains a serializable object in the Java programming language ("Java object"). It inherits from the Message interface and adds a body containing a single reference to an object. Only Serializable Java objects can be used.

If a collection of Java objects must be sent, one of the Collection classes provided since JDK 1.2 can be used.

When a client receives an ObjectMessage, it is in read-only mode. If a client attempts to write to the message at this point, a MessageNotWriteableException is thrown. If clearBody is called, the message can now be both read from and written to.

Also see:

javax.jms.Session#createObjectMessage()

javax.jms.Session#createObjectMessage(Serializable)

javax.jms.BytesMessage

javax.jms.MapMessage

javax.jms.Message

javax.jms.StreamMessage

javax.jms.TextMessage

Method from javax.jms.ObjectMessage Summary:
getObject, setObject

Method from javax.jms.ObjectMessage Detail:
public Serializable getObject() throws JMSException Gets the serializable object containing this message's data. The default value is null.
public void setObject(Serializable object) throws JMSException Sets the serializable object containing this message's data. It is important to note that an `ObjectMessage` contains a snapshot of the object at the time `setObject()` is called; subsequent modifications of the object will have no effect on the `ObjectMessage` body.

Method from javax.jms.ObjectMessage Detail:

 public Serializable getObject() throws JMSExceptionGets the serializable object containing this message's data. The 
default value is null.

 public  void setObject(Serializable object) throws JMSExceptionSets the serializable object containing this message's data.
It is important to note that an ObjectMessage
contains a snapshot of the object at the time setObject()
is called; subsequent modifications of the object will have no 
effect on the ObjectMessage body.