ObjectMessage object is used to send a message that contains a serializable object in the Java programming language ("Java object").
More...
#include <javax_jms_ObjectMessage.h>
Inheritance diagram for javax::jms::ObjectMessage:


Public Types | |
| enum | { xmogDefaultFlags = xmog_base::GLOBAL, xmogMajorVersion = 3, xmogMinorVersion = 2, xmogPatchVersion = 9, xmogBuildNumber = 2047 } |
|
typedef ::xmog_java_array_template< ::javax::jms::ObjectMessage > | array1D |
|
typedef ::xmog_java_array_template< ::xmog_java_array_template< ::javax::jms::ObjectMessage > > | array2D |
Public Member Functions | |
| virtual ::java::io::Serializable | getObject (::xmog_localenv *p_xenv=NULL, xmog_flags f_xflags=xmogDefaultFlags) |
| Gets the serializable object containing this message's data. | |
| virtual void | setObject (const ::java::io::Serializable &object,::xmog_localenv *p_xenv=NULL, xmog_flags f_xflags=xmogDefaultFlags) |
| Sets the serializable object containing this message's data. | |
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.
Rich Burridge
|
||||||||||||
|
Gets the serializable object containing this message's data. The default value is null.
|
|
||||||||||||||||
|
Sets the serializable object containing this message's data.
It is important to note that an
|
1.4.1