Re: [infinispan-dev] Multiple Spring modules
Hey!
After several discussions we decided to create 2 separate modules for
Spring 3 and Spring 4 support.
As Gustavo mentioned, there are a lot of new things in Spring 4.1 which
are connected to caching. Once we start supporting Spring 3 and 4
integration using the same jar - new features might be hard (if not
impossible) to introduce. Having 2 separate jars gives us flexibility
which might be useful in the future.
The code might be found here:
*https://github.com/infinispan/infinispan/pull/2957*
Best regards
Sebastian
On 10/14/2014 03:41 PM, Gustavo Fernandes wrote:
I prefer #1, since it decouples Spring 3 from Spring 4. For example,
Spring 4.1 is bringing many improvements on Cache [1], which I'm not
sure if it will available on 3.2.x maintenance branch.
[1] http://spring.io/blog/2014/06/16/further-cache-improvements-in-spring-4-1
<slaskawi(a)redhat.com> wrote:
>
> 1. Create copy of Spring 3 module and put everything into newly created
> Spring 4, then update versions and implement new methods in Cache
> interface.
> Pros:
> - 1 OSGi bundle - transparent upgrade - just replace spring bundle
> - Easy to maintain Spring 4 only fixes
> Cons:
> - Code duplication
>
Attachments:
- attachment.html (text/html — 2.0 KB)