Packages
Package	Description
asia.stampy.client.message	Provides the abstract client header classes
asia.stampy.client.message.abort	Provides the STOMP 1.2 ABORT header and message classes
asia.stampy.client.message.ack	Provides the STOMP 1.2 ACK header and message classes
asia.stampy.client.message.begin	Provides the STOMP 1.2 BEGIN header and message classes
asia.stampy.client.message.commit	Provides the STOMP 1.2 COMMIT header and message classes
asia.stampy.client.message.connect	Provides the STOMP 1.2 COMMIT header and message classes
asia.stampy.client.message.disconnect	Provides the STOMP 1.2 DISCONNECT header and message classes
asia.stampy.client.message.nack	Provides the STOMP 1.2 NACK header and message classes
asia.stampy.client.message.send	Provides the STOMP 1.2 SEND header and message classes
asia.stampy.client.message.stomp	Provides the STOMP 1.2 STOMP header and message classes
asia.stampy.client.message.subscribe	Provides the STOMP 1.2 SUBSCRIBE header and message classes
asia.stampy.client.message.unsubscribe	Provides the STOMP 1.2 UNSUBSCRIBE header and message classes
asia.stampy.common	Provides common classes
asia.stampy.common.message	Provides the STOMP 1.2 common interfaces and super classes for messages
asia.stampy.common.parsing	Provides message parsing tools
asia.stampy.common.serialization	Provides serialization tools
asia.stampy.server.message.connected	Provides the STOMP 1.2 CONNECTED header and message classes
asia.stampy.server.message.error	Provides the STOMP 1.2 ERROR header and message classes
asia.stampy.server.message.message	Provides the STOMP 1.2 MESSAGE header and message classes
asia.stampy.server.message.receipt	Provides the STOMP 1.2 RECEIPT header and message classes

Stampy, a Java implementation of the STOMP 1.2 specification

Release 1.0-RELEASE, 18-02-2013

stampy-core-1.0-RELEASE

This library provides class representations of STOMP 1.2 messages and the ability to convert to and from the classes. It can be used with the additional Stampy libraries or it can be used with existing STOMP client or server implementations.

Design considerations

Compiled for Java 5 compatibility
Ease of configuration and use
DI framework-friendly
Minimal dependencies
Reliable
Extensible

Dependencies

<dependency org="org.slf4j" name="slf4j-api" rev="1.7.2"/>

<dependency org="commons-lang" name="commons-lang" rev="2.6"/>

<dependency org="commons-codec" name="commons-codec" rev="1.7"/>

Messages

All STOMP message classes implement the StampyMessage interface. Message classes typically have at least two constructors, one blank & the other with parameters - the parameterized constructors are all the mandatory header values that must be set for a valid STOMP message. Should any mandatory header information be missing an exception will be thrown when the message's

validate()

method is called.

Each StampyMessage class has an associated header class which can be obtained by calling the

getHeader()

method. The header classes are wrappers around a map which manages the key value pairs. Known key names have their own getter and setter methods; any key value pair can be added to a Stampy message header.

Note: should a header key already exist in the map any subsequent adds for that key will be ignored. This is to enforce the specification: If a client or a server receives repeated frame header entries, only the first header entry SHOULD be used as the value of header entry. Subsequent values are only used to maintain a history of state changes of the header and MAY be ignored. To replace an existing key the header's

removeHeader(existingKey)

method must be called first.

Parsing

A message parser is included for converting the raw string messages to their associated StampyMessage objects.

Message Bodies

Any STOMP message that has a body can accept a string as the body as well as any Java serializable object. The mime type used by Stampy to represent such serialized objects is

java/base64

Encoding to and from Base64 is handled by the message superclasses & the parser, respectively.