The Oracle Commerce Platform’s JMS providers use the following message format conventions, based on a subset of the JMS message options:
Messages are of type
javax.jms.ObjectMessage
. The objects stored in theObjectMessage
are serializable Java Beans whose properties contain the message’s data. These Java Beans are called message beans.The class names for the Message Beans all end with
Message
—for example,atg.nucleus.dms.DASMessage
.The
JMSType
header is used to identify the type of message being fired.JMSType
names follow package name conventions—for example,atg.das.Startup
. TheJMSType
name does not need to be an actual Java class name; it follows the package naming conventions to avoid collisions with other JMS applications.Each
JMSType
corresponds to exactly one Message Bean class. For example, a message ofJMSType
atg.das.Startup
is always anObjectMessage
containing a bean of typeatg.nucleus.dms.DASMessage
. MultipleJMSTypes
can correspond to the same Message Bean class. For example,JMSType
atg.das.Shutdown
also corresponds toatg.nucleus.dms.DASMessage
.Messages avoid the use of application-specific header values. All such values are instead represented as properties of the contained message bean.