[
https://issues.jboss.org/browse/ISPN-4686?page=com.atlassian.jira.plugin....
]
Paul Ferraro commented on ISPN-4686:
------------------------------------
Other incompatiblities:
* org.infinispan.manager.AbstractDelegatingEmbeddedCacheManager ->
org.infinispan.manager.impl.AbstractDelegatingEmbeddedCacheManager
* org.infinispan.affinity.KeyAffinityServiceImpl ->
org.infinispan.affinity.impl.KeyAffinityServiceImpl
* org.infinispan.persistence.jdbc.DatabaseType ->
org.infinispan.persistence.jdbc.Dialect
*
org.infinispan.distribution.ch.[Default|Replicated|Sync|TopologyAware|TopologyAware]SyncConsistentHashFactory
->
org.infinispan.distribution.ch.impl.[Default|Replicated|Sync|TopologyAware|TopologyAwareSync]ConsistentHashFactory
Make Infinispan 7.0 binary compatible with 6.x
----------------------------------------------
Key: ISPN-4686
URL:
https://issues.jboss.org/browse/ISPN-4686
Project: Infinispan
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 7.0.0.Beta1
Reporter: Galder ZamarreƱo
Assignee: Galder ZamarreƱo
Fix For: 7.0.0.Beta2
The idea here is to try to produce a Infinispan 7.0 jar that's binary compatible with
6.0 in order to ease upgrading. So far, the following elements have been found to be
problematic:
* FileLookupFactory -> FileLookup changes - ISPN-3850
* JBossStandaloneJTAManagerLookup.init changes - ISPN-3850
* org.infinispan.AbstractDelegatingAdvancedCache refactoring to
org.infinispan.cache.impl.AbstractDelegatingAdvancedCache - ISPN-4074
XML configuration stays apart since one of the key aspects of 7.0 is to produce WF-like
configuration that's as close as possible, to improve usability between library and
server mode.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)