[infinispan-issues] [JBoss JIRA] (ISPN-4686) Make Infinispan 7.0 binary compatible with 6.x
[
https://issues.jboss.org/browse/ISPN-4686?page=com.atlassian.jira.plugin....
]
Dan Berindei commented on ISPN-4686:
------------------------------------
[~NadirX] the abstract delegating cache/cache manager classes were actually meant for end
users to subclass so that they wouldn't break when we added a new method (ISPN-1526).
We also expect the user to select a consistent hash factory by specifying the full class
name, so I would consider those class names part of the public API.
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
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)