[rabbitmq-discuss] AMQP message "Type" - STOMP mapping?

Simon MacMullen simon at rabbitmq.com
Wed Sep 12 15:24:19 BST 2012

On 11/09/12 14:41, Michael Justin wrote:
> do I understand correctly that the AMQP message property "Type" is
> supported between the C# client (RabbitMQ's .NET library) and the broker
> but the value of this property is not transported on to STOMP clients as
> a message header property?


> In the Delphi/Habari STOMP client, the messages can have a property
> "JMSType" which will be transmitted as a STOMP header property ("type").
> Does a workaround exist to exchange the AMQP "Type" property of a
> message with STOMP clients?

I'm not sure there is one, other than to say "use 'content-type' 
instead". Which may not be exactly what you wanted to hear.

For reasons lost in the mists of time our STOMP adapter ignores:

* expiration
* timestamp
* type
* user-id
* app-id

I'm not sure there's any reason not just to add support for these, so 
you could hold out for a future release.

Cheers, Simon

Simon MacMullen
RabbitMQ, VMware

More information about the rabbitmq-discuss mailing list