[
https://issues.apache.org/activemq/browse/AMQ-1609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=42161#action_42161
]
Michael Justin commented on AMQ-1609:
-------------------------------------
I am not sure if calling it STOMP 1.1 is neccessary (I am no protocol/interop
guru), but I think yes it would be helpful. It would indicate that there are
different protocol levels, and some features will not work on older versions of
ActiveMQ.
BTW I correct myself, it should be "property-transformation:json" instead of
"property-encoding:json" because encoding could be misunderstood as character
encoding.
Kind Regards
Michael
> STOMP messages only support properties with data type String
> -------------------------------------------------------------
>
> Key: AMQ-1609
> URL: https://issues.apache.org/activemq/browse/AMQ-1609
> Project: ActiveMQ
> Issue Type: Improvement
> Reporter: Michael Justin
>
> Currently the STOMP connector seems to support only string type message
> properties.
> As an effect, subscription selectors like color = 'blue' AND weight > 2500
> will not work (if the message has been sent using STOMP, the weight property
> will be a string).
> I suggest to implement typed properties in the Stomp protocol which could be
> serialized in a platform-independent way.
> In addtion , if I understand the OpenWire documentation correctly, the
> OpenWire protocol supports some simple datatypes, but not - for example -
> Date, which would be easy to map to a long value.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
