activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (ARTEMIS-1611) Artemis transformer interface is not backwards compatible
Date Thu, 18 Jan 2018 14:31:00 GMT


ASF GitHub Bot commented on ARTEMIS-1611:

Github user mtaylor commented on the issue:
    @jmesnil Made the changes you suggested.  @clebertsuconic I agree with @jmesnil  that
adding back the original types is the clearest and safest thing to do, with the disadvantage
of add more deprecated code back.

> Artemis transformer interface is not backwards compatible
> ---------------------------------------------------------
>                 Key: ARTEMIS-1611
>                 URL:
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 2.4.0
>         Environment:  
>            Reporter: Jeff Mesnil
>            Priority: Major
> We have users of Artemis 1.x that uses the transformer interface defined in org.apache.activemq.artemis.core.server.cluster.Transformer.
> This class was moved in Artemis 2.x in an incompatible way: [] that
redirects to []
> We are updating Artemis 2.x but it breaks the client configuration that was using the
old interface.
> We have strong requirement for backwards compatibility and we'd like to come up with
a solution so that the new interface could be made backwards compatible with the existing
> Would it be possible sense to reintroduce the old interface in the server.cluster package
so that old code would still be able to run with Artemis 2.x?

This message was sent by Atlassian JIRA

View raw message