You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Albert Strasheim (JIRA)" <ji...@apache.org> on 2006/12/23 16:59:02 UTC
[jira] Created: (AMQCPP-32) Stomp messages don't preserve property
types: please document this behaviour
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
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
[jira] Commented: (AMQCPP-32) Stomp messages don't preserve
property types: please document this behaviour
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQCPP-32?page=comments#action_37760 ]
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: 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
>
> 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
[jira] Updated: (AMQCPP-32) Stomp messages don't preserve property
types: please document this behaviour
Posted by "Nathan Mittler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQCPP-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nathan Mittler updated AMQCPP-32:
---------------------------------
Fix Version/s: 1.1
> 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
> Fix For: 1.1
>
>
> 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
[jira] Commented: (AMQCPP-32) Stomp messages don't preserve
property types: please document this behaviour
Posted by "Albert Strasheim (JIRA)" <ji...@apache.org>.
[ 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
[jira] Closed: (AMQCPP-32) Stomp messages don't preserve property
types: please document this behaviour
Posted by "Nathan Mittler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQCPP-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Nathan Mittler closed AMQCPP-32.
--------------------------------
Resolution: Fixed
I have documented the behavior here http://www.activemq.org/site/activemq-cpp-stomp.html
> 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
> Fix For: 1.1
>
>
> 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
[jira] Updated: (AMQCPP-32) Stomp messages don't preserve property
types: please document this behaviour
Posted by "Timothy Bish (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQCPP-32?page=all ]
Timothy Bish updated AMQCPP-32:
-------------------------------
Priority: Trivial (was: Major)
> 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
[jira] Commented: (AMQCPP-32) Stomp messages don't preserve
property types: please document this behaviour
Posted by "Nathan Mittler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/activemq/browse/AMQCPP-32?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_37832 ]
Nathan Mittler commented on AMQCPP-32:
--------------------------------------
I agree with Tim - this really should be commented on the wiki page. The user isn't going to be looking into the code comments - rather, they should only be looking at the CMS API. The CMS API isn't going to tell them the specific quirks of a particular implementation. I'll take this issue and will update the wiki page accordingly.
> 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
> Fix For: 1.1
>
>
> 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