[ http://issues.apache.org/jira/browse/QPID-9?page=comments#action_12456438 ] Martin Ritchie commented on QPID-9: -----------------------------------
Of course JMS requirements are not quite compatible. 3.5.1 Property Names • Identifiers: - An identifier is an unlimited-length character sequence that must begin with a Java identifier start character; all following characters must be Java identifier part characters. An identifier start character is any character for which the method Character.isJavaIdentifierStart returns true. This includes '_' and '$'. An identifier part character is any character for which the method Character.isJavaIdentifierPart returns true. - Identifiers cannot be the names NULL, TRUE, or FALSE. Allowing an unlimited-lenght character sequence compared to AMQP's 128 limit. > 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 > Reporter: Alan Conway > Assigned To: Martin Ritchie > Priority: Minor > > 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
