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

["Martin Ritchie (JIRA)" <qp...@incubator.apache.org>]

    [ http://issues.apache.org/jira/browse/QPID-9?page=comments#action_12455947 ] 
            
Martin Ritchie commented on QPID-9:
-----------------------------------

r482733 the amqp field table does not support sufficent types to allow all JMS primatives to be preserved during transportation. This update encodes all java types using the xml format used by MapMessage.

However this doesn't address missing type support detailed in this JIRA. However from a JMS compliance point of view this won't affect us. We will have to re-address this issue as we develop an AMQP API level as currently we cannot build an interoperable java AMQP only client without these changes.

> 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