activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Timothy Bish (JIRA)" <>
Subject [jira] Commented: (AMQCPP-32) Stomp messages don't preserve property types: please document this behaviour
Date Sat, 23 Dec 2006 18:17:03 GMT
    [ ] 
Timothy Bish commented on AMQCPP-32:

This behavior is exactly what you'd expect from stomp as its a text based protocol.  I'd rather
the documentation go somewhere on the Wiki (any volunteers?).  If you'd like to come up with
some useful documentation we are always willing to accept patches.  

The only way I would want to add this sort of functionality to Stomp is if the Stomp protocol
itself evolved to include this in its definitions.  Stomp is meant to be simple and it succeeds
at that quite well.  

> Stomp messages don't preserve property types: please document this behaviour
> ----------------------------------------------------------------------------
>                 Key: AMQCPP-32
>                 URL:
>             Project: ActiveMQ C++ Client
>          Issue Type: Wish
>          Components: Stomp
>    Affects Versions: 1.1
>            Reporter: Albert Strasheim
>         Assigned To: Nathan Mittler
> I am producing messages from Java and C++ using ActiveMQ and AMQCPP, respectively. Messages
I produce have an int property set on them which I want to select on, again in Java or C++.
> As far as I can tell from the [Stomp Protocol specification|]
there is no way to specify the types of message headers. As a result, all the messages end
up with String properties as can be be seen in the unmarshal method of [org.apache.activemq.transport.stomp|].
> I can work around this problem by selecting on id=123||id='123' in both Java and C++,
but it seems a bit suboptimal.
> At least, this issue should be documented somewhere in activemq::connector::stomp::commands::StompMessage
to help other people who can't figure out why their selectors don't work.
> We could consider adding a function that allows the user to specify that Stomp message
properties should be sent in a type safe manner, and then prepend some kind of string to the
property name to indicate the type. StompWireFormat on the Java side could check for this
case and set the typed properties accordingly. This is probably too much of a hack -- people
who want typed properties to work right can use Openwire in the (hopefully) near future.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message