[ https://issues.apache.org/activemq/browse/AMQCPP-32?page=comments#action_37761 ] Albert Strasheim commented on AMQCPP-32: ----------------------------------------
I think I'll make a documentation patch. Thanks. > Stomp messages don't preserve property types: please document this behaviour > ---------------------------------------------------------------------------- > > Key: AMQCPP-32 > URL: https://issues.apache.org/activemq/browse/AMQCPP-32 > Project: ActiveMQ C++ Client > Issue Type: Wish > Components: Stomp > Affects Versions: 1.1 > Reporter: Albert Strasheim > Assigned To: Nathan Mittler > Priority: Trivial > > 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|http://stomp.codehaus.org/Protocol] 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|http://svn.apache.org/viewvc/incubator/activemq/trunk/activemq-core/src/main/java/org/apache/activemq/transport/stomp/StompWireFormat.java?revision=470398&view=markup]. > 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: https://issues.apache.org/activemq/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
