You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Timothy Bish (JIRA)" <ji...@apache.org> on 2009/10/07 21:13:52 UTC
[jira] Assigned: (AMQNET-193) Add support for read-only bodies and
properties for all of the NMS message types
[ https://issues.apache.org/activemq/browse/AMQNET-193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Timothy Bish reassigned AMQNET-193:
-----------------------------------
Assignee: Timothy Bish (was: Jim Gomes)
> Add support for read-only bodies and properties for all of the NMS message types
> --------------------------------------------------------------------------------
>
> Key: AMQNET-193
> URL: https://issues.apache.org/activemq/browse/AMQNET-193
> Project: ActiveMQ .Net
> Issue Type: Improvement
> Components: ActiveMQ
> Affects Versions: 1.1.0
> Reporter: Timothy Bish
> Assignee: Timothy Bish
> Priority: Minor
> Fix For: 1.2.0
>
>
> The StreamMessage and BytesMessage now support read-only and write-only states for the message bodies, the other messages need to be updated to honor the read-only states as well.
> * TextMessage should throw MessageNotWritableException in the Set method for Text.
> * MapMessage should throw MessageNotWritableException in the Set methods for the body.
> * all messages should have read-only states for the Properties.
> * calling ClearBody on any message returns it to either Write-Only or read / write mode.
> * calling ClearProperties on any message returns them to Read / Write mode.
> Messages are tagged as read-only when they are sent and when received.
> This will result in the message's behaving the same as their JMS and CMS counterparts.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.