You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Rob Godfrey (JIRA)" <qp...@incubator.apache.org> on 2006/12/22 13:00:23 UTC

[jira] Created: (QPID-228) Re-implement MapMessage in terms of StreamMessage encoding

Re-implement MapMessage in terms of StreamMessage encoding
----------------------------------------------------------

                 Key: QPID-228
                 URL: http://issues.apache.org/jira/browse/QPID-228
             Project: Qpid
          Issue Type: Bug
          Components: Java Client, JMS Compliance
            Reporter: Rob Godfrey


The current implementation of MapMessage uses the AMQP FieldTable type which has several implicit limitations of the values held as keys and as values.  Instead implement the MapMessage in the same way as a StreamMessage with first the number of entries, followed by, for each entry, the encoded string key, and then the encoded object value.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Updated: (QPID-228) Re-implement MapMessage in terms of StreamMessage encoding

Posted by "Rob Godfrey (JIRA)" <qp...@incubator.apache.org>.
     [ http://issues.apache.org/jira/browse/QPID-228?page=all ]

Rob Godfrey updated QPID-228:
-----------------------------

    Attachment: QPID-228.patch

Fixes as described in the original description.

Passes all original unit tests.

Also small fix to the code which was in StreamMessage to handle better the case when readObject() is called for a byte[]

> Re-implement MapMessage in terms of StreamMessage encoding
> ----------------------------------------------------------
>
>                 Key: QPID-228
>                 URL: http://issues.apache.org/jira/browse/QPID-228
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Client, JMS Compliance
>            Reporter: Rob Godfrey
>         Attachments: QPID-228.patch
>
>
> The current implementation of MapMessage uses the AMQP FieldTable type which has several implicit limitations of the values held as keys and as values.  Instead implement the MapMessage in the same way as a StreamMessage with first the number of entries, followed by, for each entry, the encoded string key, and then the encoded object value.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Resolved: (QPID-228) Re-implement MapMessage in terms of StreamMessage encoding

Posted by "Robert Greig (JIRA)" <qp...@incubator.apache.org>.
     [ http://issues.apache.org/jira/browse/QPID-228?page=all ]

Robert Greig resolved QPID-228.
-------------------------------

    Fix Version/s: M2
       Resolution: Fixed

Committed to svn rev 489644

> Re-implement MapMessage in terms of StreamMessage encoding
> ----------------------------------------------------------
>
>                 Key: QPID-228
>                 URL: http://issues.apache.org/jira/browse/QPID-228
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Client, JMS Compliance
>            Reporter: Rob Godfrey
>             Fix For: M2
>
>         Attachments: QPID-228.patch
>
>
> The current implementation of MapMessage uses the AMQP FieldTable type which has several implicit limitations of the values held as keys and as values.  Instead implement the MapMessage in the same way as a StreamMessage with first the number of entries, followed by, for each entry, the encoded string key, and then the encoded object value.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Assigned: (QPID-228) Re-implement MapMessage in terms of StreamMessage encoding

Posted by "Rob Godfrey (JIRA)" <qp...@incubator.apache.org>.
     [ https://issues.apache.org/jira/browse/QPID-228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rob Godfrey reassigned QPID-228:
--------------------------------

    Assignee: Rob Godfrey

> Re-implement MapMessage in terms of StreamMessage encoding
> ----------------------------------------------------------
>
>                 Key: QPID-228
>                 URL: https://issues.apache.org/jira/browse/QPID-228
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Client, JMS Compliance
>            Reporter: Rob Godfrey
>         Assigned To: Rob Godfrey
>             Fix For: M2
>
>         Attachments: QPID-228.patch
>
>
> The current implementation of MapMessage uses the AMQP FieldTable type which has several implicit limitations of the values held as keys and as values.  Instead implement the MapMessage in the same way as a StreamMessage with first the number of entries, followed by, for each entry, the encoded string key, and then the encoded object value.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.