You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2017/04/14 15:02:41 UTC
[jira] [Commented] (QPID-7644) [Java Broker] [AMQP 1.0] Remove
non-standard support for UTF-16 Strings from the AMQP type system
[ https://issues.apache.org/jira/browse/QPID-7644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15969115#comment-15969115 ]
ASF subversion and git services commented on QPID-7644:
-------------------------------------------------------
Commit 1791375 from [~lorenz.quack] in branch 'java/trunk'
[ https://svn.apache.org/r1791375 ]
QPID-7644: [Java Broker] [AMQP 1.0] Remove non-standard support for UTF-16 Strings from the AMQP type system
> [Java Broker] [AMQP 1.0] Remove non-standard support for UTF-16 Strings from the AMQP type system
> -------------------------------------------------------------------------------------------------
>
> Key: QPID-7644
> URL: https://issues.apache.org/jira/browse/QPID-7644
> Project: Qpid
> Issue Type: Bug
> Components: Java Broker
> Reporter: Lorenz Quack
> Fix For: qpid-java-broker-7.0.0
>
>
> Currently the Broker has facilities to support for UTF-16 strings using the 0xA2 and 0xB2 constructors in the AMQP 1.0 type system. Those constructors are historic - they were removed from the spec before it was finalised.
> To avoid incompatibilities with other AMQP 1.0 products we should remove them.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org