You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Arnaud Simon (JIRA)" <qp...@incubator.apache.org> on 2009/01/29 10:31:59 UTC
[jira] Created: (QPID-1620) IMessage wrapper
IMessage wrapper
----------------
Key: QPID-1620
URL: https://issues.apache.org/jira/browse/QPID-1620
Project: Qpid
Issue Type: Improvement
Components: Dot Net Client
Affects Versions: M4
Reporter: Arnaud Simon
Fix For: M5
Introduce a wrapper around IMessage that would hide the AMQP specificities. We should decide of the API of this wraper. A suggestion would be to at least expose the message headers and the underlying IMessage.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
[jira] Commented: (QPID-1620) IMessage wrapper
Posted by "Shahbaz Chaudhary (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-1620?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12668567#action_12668567 ]
Shahbaz Chaudhary commented on QPID-1620:
-----------------------------------------
Currently, in order to get to the content most people are interested in, they have to get ApplicationHeader out of IMessage. If a wrapper is put around IMessage, I think it should directly expose ApplicationHeader fields.
For example, QMessage (the wrapper) may contain IMessage:
QMessage m = ...
object x=m.getIMessage()...
But I'd like to get the payload of the message directly:
int y = m["fieldName"]
> IMessage wrapper
> ----------------
>
> Key: QPID-1620
> URL: https://issues.apache.org/jira/browse/QPID-1620
> Project: Qpid
> Issue Type: Improvement
> Components: Dot Net Client
> Affects Versions: M4
> Reporter: Arnaud Simon
> Fix For: M5
>
>
> Introduce a wrapper around IMessage that would hide the AMQP specificities. We should decide of the API of this wraper. A suggestion would be to at least expose the message headers and the underlying IMessage.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org
[jira] Updated: (QPID-1620) IMessage wrapper
Posted by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-1620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Ritchie updated QPID-1620:
---------------------------------
Fix Version/s: (was: M5)
> IMessage wrapper
> ----------------
>
> Key: QPID-1620
> URL: https://issues.apache.org/jira/browse/QPID-1620
> Project: Qpid
> Issue Type: Improvement
> Components: Dot Net Client
> Affects Versions: M4
> Reporter: Arnaud Simon
>
> Introduce a wrapper around IMessage that would hide the AMQP specificities. We should decide of the API of this wraper. A suggestion would be to at least expose the message headers and the underlying IMessage.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org