You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Jim Gomes (JIRA)" <ji...@apache.org> on 2009/09/22 20:55:05 UTC
[jira] Updated: (AMQNET-42) Add support for typesafe properties and
headers over STOMP
[ https://issues.apache.org/activemq/browse/AMQNET-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jim Gomes updated AMQNET-42:
----------------------------
Fix Version/s: (was: 1.2.0)
Summary: Add support for typesafe properties and headers over STOMP (was: add support for typesafe properties and headers over STOMP)
Post-poning to unknown release, since this enhancement is dependent upon the STOMP protocol specification being upgraded to support this feature first.
> Add support for typesafe properties and headers over STOMP
> ----------------------------------------------------------
>
> Key: AMQNET-42
> URL: https://issues.apache.org/activemq/browse/AMQNET-42
> Project: ActiveMQ .Net
> Issue Type: New Feature
> Components: ActiveMQ
> Reporter: James Strachan
> Assignee: James Strachan
>
> 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.
-
You can reply to this email to add a comment to the issue online.