activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeff Mesnil (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (ARTEMIS-1611) Artemis transformer interface is not backwards compatible
Date Tue, 16 Jan 2018 16:11:04 GMT

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

Jeff Mesnil updated ARTEMIS-1611:
---------------------------------
    Description: 
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: [https://github.com/apache/activemq-artemis/blob/master/artemis-server/src/main/java/org/apache/activemq/artemis/core/server/cluster/Transformer.java] that
redirects to [https://github.com/apache/activemq-artemis/blob/master/artemis-server/src/main/java/org/apache/activemq/artemis/core/server/transformer/Transformer.java]

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 one.

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?

 

> Artemis transformer interface is not backwards compatible
> ---------------------------------------------------------
>
>                 Key: ARTEMIS-1611
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-1611
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 2.4.0
>         Environment: 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: [https://github.com/apache/activemq-artemis/blob/master/artemis-server/src/main/java/org/apache/activemq/artemis/core/server/cluster/Transformer.java] that
redirects to [https://github.com/apache/activemq-artemis/blob/master/artemis-server/src/main/java/org/apache/activemq/artemis/core/server/transformer/Transformer.java]
> 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
one.
> 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?
>  
>            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: [https://github.com/apache/activemq-artemis/blob/master/artemis-server/src/main/java/org/apache/activemq/artemis/core/server/cluster/Transformer.java] that
redirects to [https://github.com/apache/activemq-artemis/blob/master/artemis-server/src/main/java/org/apache/activemq/artemis/core/server/transformer/Transformer.java]
> 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
one.
> 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
(v7.6.3#76005)

Mime
View raw message