add received routing key and received exchange names to Message so that those fields (particularly routing key) can be used to send messages down different streams in storm using MultiStreamSpout
back to snapshot
Allow MessageScheme's to be aware of RabbitMQ messages.

Currently, a message scheme only has access to a message's
payload. This means that if you need access to routing key,
time stamp or any other "meta" information from rabbitmq
within your topology, you can't use storm-rabbitmq.

This change allows you to write MessageSchemes that have
can create tuples that include not just payload data
but any additional rabbitmq envelope information that you
may need.

Previously, this information was only available when
emitting a tuple, not during tuple creation.
Back to snapshot.
RabbitMQ aware message scheme.

Allow access to rabbitmq message info such as timestamp etc
via deserialized tuple.
upgrade storm to 0.9.0.1 and slf4j-api to 1.6.6 (to match sl4j version in storm 0.9.0.1)
back to snapshot
Make RabbitMQMessageScheme more flexible.

Allow it to be able to be wrapped around any
existing scheme without having to change any code.
You can supply a field name for both properties and
envelope and access them at the first bolt that
talks to the spout.

If you need information specific to RabbitMQ, you
need to grab it there and thread through the rest
of your topology. This means, that is you were using,
say SimpleJsonScheme, you wouldn't need to
change any code that was looking for the field name:

"object".

Field ordering also renames unchanged with
envelope and properties being added at the end.
Merge with remote.