To ensure that both XMS applications can exchange messages with a WebSphere MQ JMS application both must be able to interpret the application data in the body of a message in the same way.
For this reason, each element of application data written in the body of a message by an XMS application must have one of the data types listed in Table 1. For each XMS data type, the table shows the compatible Java data type. XMS provides the methods to write elements of application data only with these data types.
XMS data type | Represents | Compatible Java data type |
---|---|---|
xmsBOOL | The boolean value xmsTRUE or xmsFALSE | boolean |
xmsCHAR16 | Double byte character | char |
xmsSBYTE | Signed 8-bit integer | byte |
xmsSHORT | Signed 16-bit integer | short |
xmsINT | Signed 32-bit integer | int |
xmsLONG | Signed 64-bit integer | long |
xmsFLOAT | Signed floating point number | float |
xmsDOUBLE | Signed double precision floating point number | double |
String | String of characters | String |
For information about the size, maximum value and minimum value of each of these data types, see XMS primitive types.