The QmfData class defines a collection of named data values. Optionally, a string tag, or "sub-type" may be associated with each data item. This tag may be used by an application to annotate the data item. (Note the tag implementation is TBD).
In QMFv2, message bodies are AMQP maps and are therefore easily extended without causing backward compatibility problems. Another benefit of the map-message format is that all messages can be fully parsed when received without the need for external schema data
This class is the base class for all QMF2 Data Types in this implementation. It is intended to provide a useful wrapper for the underlying Map, supplying accessor and mutator methods that give an element of type safety (for example strings appear to be encoded as a mixture of byte[] and String depending of the agent, so this class checks for this in its getString())
The following diagram represents the QmfData class hierarchy.
@author Fraser Adams
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|