You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Kim van der Riet (JIRA)" <ji...@apache.org> on 2018/03/05 21:37:00 UTC
[jira] [Reopened] (QPIDIT-114) [AMQP.NetLite] AMQP char type is not
supported, but is not excluded from test
[ https://issues.apache.org/jira/browse/QPIDIT-114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kim van der Riet reopened QPIDIT-114:
-------------------------------------
Assignee: Chuck Rolke (was: Kim van der Riet)
I received the following comment from the Azure AMQP.NetLite folks after creating a Jira for the lack of char support - AMQP char type not supported (#259):
{quote}It is supported by the library. The tests need to be updated to include 'char' type.
{quote}
> [AMQP.NetLite] AMQP char type is not supported, but is not excluded from test
> -----------------------------------------------------------------------------
>
> Key: QPIDIT-114
> URL: https://issues.apache.org/jira/browse/QPIDIT-114
> Project: Apache QPID Interoperability Test Suite
> Issue Type: Bug
> Components: .Net Lite Shim, AMQP Types Test
> Affects Versions: 0.1.0
> Reporter: Kim van der Riet
> Assignee: Chuck Rolke
> Priority: Major
> Fix For: 0.2.0
>
>
> When the amqp_types_test is run against the ActiveMQ broker (which can handle AMQP type char, unlike several other brokers), the tests of AMQP type {{char}} fail with an error message from the AMQP.NetLite shims:
> {noformat}
> System.ApplicationException: Sender can not encode base type: char{noformat}
> As a mechanism exists in each test to exclude AMQP types based on the client being run, this should be added.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org