You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@qpid.apache.org by "Martin Ritchie (JIRA)" <qp...@incubator.apache.org> on 2006/12/01 16:17:21 UTC

[jira] Updated: (QPID-9) Missing support for field table types D, T and F

     [ http://issues.apache.org/jira/browse/QPID-9?page=all ]

Martin Ritchie updated QPID-9:
------------------------------

      Component/s: Java Common
                   JMS Compliance
    Fix Version/s: M2
      Description: 
The spec defines these additional types. This area may be in flux so check spec status before implementing:
/ 'D' decimal-value
/ 'T' timestamp
/ 'F' field-table

Needs to be addressed across all languages and the python headers exchange tests should test all types.

The field table also does not support sufficient types of values for JMS support see message thread:

https://amqp.108.redhat.com/servlets/ReadMsg?list=dev&msgNo=169

Possible a possible temporary work around would be to use encoded String values 

  was:
The spec defines these additional types. This area may be in flux so check spec status before implementing:
/ 'D' decimal-value
/ 'T' timestamp
/ 'F' field-table

Needs to be addressed across all languages and the python headers exchange tests should test all types.

         Assignee: Martin Ritchie
         Priority: Blocker  (was: Major)

> Missing support for field table types D, T and F
> ------------------------------------------------
>
>                 Key: QPID-9
>                 URL: http://issues.apache.org/jira/browse/QPID-9
>             Project: Qpid
>          Issue Type: Bug
>          Components: Java Common, JMS Compliance
>            Reporter: Alan Conway
>         Assigned To: Martin Ritchie
>            Priority: Blocker
>             Fix For: M2
>
>
> The spec defines these additional types. This area may be in flux so check spec status before implementing:
> / 'D' decimal-value
> / 'T' timestamp
> / 'F' field-table
> Needs to be addressed across all languages and the python headers exchange tests should test all types.
> The field table also does not support sufficient types of values for JMS support see message thread:
> https://amqp.108.redhat.com/servlets/ReadMsg?list=dev&msgNo=169
> Possible a possible temporary work around would be to use encoded String values 

-- 
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