[infinispan-issues] [JBoss JIRA] (ISPN-1740) Refactor internal classes to use new Configuration beans

[Manik Surtani (JIRA)]

     [ https://issues.jboss.org/browse/ISPN-1740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Manik Surtani updated ISPN-1740:
--------------------------------

        Summary: Refactor internal classes to use new Configuration beans  (was: Refactor internal classes and SPIs to use new Configuration beans)
    Description: 
The current programmatic configuration makes use of the old 5.0.x config beans internally (injection) as well as unit tests and in SPIs.

We need to refactor this internal code to use the new post-5.1 config beans.

However, the public API (DefaultCacheManager) should still support the old Configuration beans.  To do this we'd need to write something like the reverse of the LegacyConfigurationAdapter.  The LegacyConfigurationAdapter takes a 5.1 Configuration and creates a 5.0 Configuration.  We need to do this in reverse once the internals start using the new 5.1 Configuration.

Note that public API and SPI should still support the old Configuration to allow drop-in upgrades.  This includes CommandInterceptor and CacheStores.

  was:
The current programmatic configuration makes use of the old 5.0.x config beans internally (injection) as well as unit tests and in SPIs (CacheStore, CommandInterceptor, etc).

We need to refactor these SPIs and internal code to use the new post-5.1 config beans.

However, the public API (DefaultCacheManager) should still support the old Configuration beans.  To do this we'd need to write something like the reverse of the LegacyConfigurationAdapter.  The LegacyConfigurationAdapter takes a 5.1 Configuration and creates a 5.0 Configuration.  We need to do this in reverse once the internals start using the new 5.1 Configuration.


    
> Refactor internal classes to use new Configuration beans
> --------------------------------------------------------
>
>                 Key: ISPN-1740
>                 URL: https://issues.jboss.org/browse/ISPN-1740
>             Project: Infinispan
>          Issue Type: Enhancement
>          Components: Configuration
>    Affects Versions: 5.1.0.FINAL
>            Reporter: Manik Surtani
>            Assignee: Vladimir Blagojevic
>             Fix For: 5.2.0.FINAL
>
>
> The current programmatic configuration makes use of the old 5.0.x config beans internally (injection) as well as unit tests and in SPIs.
> We need to refactor this internal code to use the new post-5.1 config beans.
> However, the public API (DefaultCacheManager) should still support the old Configuration beans.  To do this we'd need to write something like the reverse of the LegacyConfigurationAdapter.  The LegacyConfigurationAdapter takes a 5.1 Configuration and creates a 5.0 Configuration.  We need to do this in reverse once the internals start using the new 5.1 Configuration.
> Note that public API and SPI should still support the old Configuration to allow drop-in upgrades.  This includes CommandInterceptor and CacheStores.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira