[jira] [Resolved] (AMQ-5850) AMQP: Broker should use 'JMS' transformer by default

["Timothy Bish (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/AMQ-5850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Timothy Bish resolved AMQ-5850.
-------------------------------
    Resolution: Fixed

> AMQP: Broker should use 'JMS' transformer by default
> ----------------------------------------------------
>
>                 Key: AMQ-5850
>                 URL: https://issues.apache.org/jira/browse/AMQ-5850
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: AMQP
>    Affects Versions: 5.10.0, 5.10.1, 5.10.2, 5.11.0, 5.11.1
>            Reporter: Timothy Bish
>            Assignee: Timothy Bish
>             Fix For: 5.12.0
>
>
> Currently the AMQP transportConnector uses the "NATIVE" transformer by default which limits the interoperability of AMQP client's and client's using other protocols as the messages they'd receive sent from any AMQP connection would be a BytesMessage with the unconverted AMQP message as the payload.
> By using the JMS transformer as the default we allow AMQP to interoperate just like all the other client connectors attempt to do.  Issues that existed previously with the JMS transformer have been pretty well ironed out now and most all AMQP features work even when using this transformer. 
> Those wishing to gain the small bit of performance that using native transformation would give and who don't require the interop between protocols can configure their transportConnector to use the NATIVE transformer via "transport.transformer=NATIVE"



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)