In This Section

Serialization and Deserialization

Applications work with messages as normal java objects. These views must be serialized into a provider specific message when sent, and when received they must be deserialized (or wrapped). The Talon Application Data Modeler generates Factory objects that facilitate The application registers the generated factories that it uses with the Talon runtime to allow deserialization of messages as they are received from the messaging provider.

The Talon Manual > Working with Messaging > image2016-5-1 20-1-11.png

Message Engine Independent Serializers

Generated Embedded Entities and Messages can be used independently of the Messaging Engine and support serializers/deserializers to byte [], ByteBuffer and json.

@Generated(value="com.neeve.adm.AdmGenerator", date="Fri Jan 23 02:03:22 PST 2015")
public interface IMyMessage extends extends IRogNode, IRogMessage {

	public final byte [] serializeToByteArray();
	public final ByteBuffer serializeToByteBuffer();
	public final String serializeToJson();
 
	public final void deserializeFromByteArray(byte[] bytes);
	public final void deserializeFromByteBuffer(ByteBuffer bytes);
	public final void deserializeFromJson(String json)
}

Message Metatadata

Field	Type	Description
Channel Identification
MessageChannelName	String	The name of the channel. This is used by the receiver to lookup the channel on which the message should be dispatched to the application.
MessageChannelId	short	The id of the channel. This is used by the receiver to lookup the channel on which the message should be dispatched to the application. Using a channel id allows for more efficient lookup of the channel, but care must be taken that the specified channel id matches that configured for receivers of the message will be flagged as an unhandled message.
Message Encoding Message encoding fields allows a receiving application to lookup a message factory and use it to deserialize or wrap a message.
MessageViewFactory	short	The id of the factory that is used to deserialize the message. This is used by the receiver to lookup the factory that is used to deserialize (or wrap) the received message payload.
MessageViewType	short	The id of the type (unique to its factory) used to deserialize the message.
MessageEncodingType	byte	The encoding type of the message. The encoding type is used by the factory to differentiate between possible encodings supported by the message, but may also be used by wire sniffers as a hint to decoding the message. Valid values are: 3: Protobuf The encoded payload is a series of google protobuf bytes 4: Xbuf The encoded payload is a series of google protobuf bytes which may use extensions employed by talon's protobuf implementat. 5: Json The encoded payload is a utf-8 encoded string with json content. 1: Custom The encoded payload is opaque bytes.
Message Sequencing Message sequencing fields allow for the receiving application to filter duplicate and out of order messages. For a given sender id and flow, an AepEngine will filter out received messages that don't have a monotonically increasing sequence number
MessageSender	int	A globally unique id that identifies the sender of a message. By default an AepEngine uses the hashcode of the engine name as the sender id.
MessageSno	long	A monotonically increasing sequence number. A sequence number of <=0 indicates that the message is not sequenced. Receivers should not perform duplicate checking on it. A sequence number of 1 indicates that the start (or restart of a stream). A receiver that receives sequence numbers 1,2,3,1,2,3 should not consider the 4th message a duplicate. Otherwise receivers should consider a sequence number not greater than the previous sequence number as a duplicate.
MessageFlow	int	Indicates the flow to which the message belongs. Flows allow for partitioning of message traffic in conjunction with application state and allow intra application state partitioning. Usage of flows is not currently supported for end users. External senders should always set the flow to 0.

MessageMetadata Class

SMA provides a helper class, com.neeve.MessageMetadata, that can be used by applications to assist in working with message metadata. This helper class provides the ability to serialize data into a binary format and also serves a view around this metadata.

The serialized form is as follows where (encoding is little endian).

Offset	Description
0	2 (version)
1	Message encoding type
2-3	Message view factory
4-5	Message view type
6-9	Message sender
10-13	Message flow
14-21	Message sequence number
22-23	Message channel id
24-25	number of characters in channel name
26...	ascii encoded characters in channel name

Sending Messages from External Applications

When integrating with legacy application that do not use the platform's message abstraction layer it is useful to understand how to populate transport level message in a manner that a Talon application can receive and deserialize them. Each bus binding implementation will transport the message in its byte encoded form along with the metadata described above using a mechanism specific to the message bus providers messaging API.

Refer to the message bus binding provider documentation for each bus for details.