[
https://issues.apache.org/jira/browse/AMQNET-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Timothy Bish resolved AMQNET-42.
--------------------------------
Resolution: Fixed
The current .NET Stomp client will attempt to convert properties out of the map
into the requested type allowing for user to get numeric and boolean types from
the stomp messages. Recent additions to ActiveMQ allows the broker to attempt
to apply selectors to properties by making best effort to cast the string
properties into the required types to match the selector expression. This
provides most of the functionality to meet the requirements of this issue. If
a future version of the Stomp spec adds a definition of how types are encoded
into headers other than as a String value we can add that support to NMS.Stomp.
> Add support for typesafe properties and headers over STOMP
> ----------------------------------------------------------
>
> Key: AMQNET-42
> URL: https://issues.apache.org/jira/browse/AMQNET-42
> Project: ActiveMQ .Net
> Issue Type: New Feature
> Components: Stomp
> Reporter: james strachan
> Assignee: Timothy Bish
> Priority: Minor
>
> When sending a message we could encode the types of fields using custom
> headers. e.g.
> stomp-int-headers: foo, bar
> stomp-double-headers: cheese
> Then when parsing an ActiveMQMessage we can coerce the values of the headers
> to their correct values.
> Similarly the STOMP wireformat can add these headers when turning a normal
> JMS/OpenWire message into Stomp
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
