[
https://issues.apache.org/jira/browse/QPIDIT-17?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14712395#comment-14712395
]
ASF subversion and git services commented on QPIDIT-17:
-------------------------------------------------------
Commit ebdacb0dd9063d73b49b681d39f7450fa05b391b in qpid-interop-test's branch
refs/heads/master from [~kpvdr]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-interop-test.git;h=ebdacb0 ]
QPIDIT-17: Add JMS test suite with Qpid-JMS and Proton-Python clients.
> Add JMS test suite
> ------------------
>
> Key: QPIDIT-17
> URL: https://issues.apache.org/jira/browse/QPIDIT-17
> Project: Apache QPID IT
> Issue Type: Task
> Components: JmsMessageTest
> Reporter: Kim van der Riet
> Assignee: Kim van der Riet
>
> The existing test, the Simple Type Test is centred around the AMQP 1.0 simple
> types, and is designed to send AMQP types between clients to check
> interoperability.
> However, in the world of JMS, this approach is not ideal, as there is no
> direct mapping between JMS message types and AMQP simple types. The idea is
> to add another test, which is centred around the five basic JMS message types
> rather than the AMQP types. This will allow these message types to drive the
> test values rather than the AMQP types, and will provide a more efficient
> mechanism for testing JMS interoperability between clients. While it may be
> possible to test between non-JMS clients, it makes sense that one or more JMS
> clients (such as qpid-jms) always be one of the two test clients.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
