[
https://issues.apache.org/activemq/browse/AMQ-1609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=42124#action_42124
]
Michael Justin commented on AMQ-1609:
-------------------------------------
I suggest to use JSON's basic type notation, for example:
SEND
destination:/queue/a
property-encoding:json
mystring:"foo"
myboolean:true
myint:911
myfloat:0.7
mynull:null
hello queue a
^@
JSON's basic types are
* Number (integer, real, or floating point)
* String (double-quoted Unicode with backslash escapement)
* Boolean (true and false)
* Array (an ordered sequence of values, comma-separated and enclosed in square
brackets)
* Object (collection of key/value pairs, comma-separated and enclosed in curly
brackets)
* null
property-encoding:json would indicate that the JSON syntax should be used to
map the properties to Java objects in the message broker
Kind Regards
Michael Justin
> 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.
