[jboss-jira] [JBoss JIRA] Moved: (JBAS-7842) CLONE -Infinispan replication configuration via @CacheConfig

[Brian Stansberry (JIRA)]

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

Brian Stansberry moved EJBTHREE-2054 to JBAS-7842:
--------------------------------------------------

        Project: JBoss Application Server  (was: EJB 3.0)
            Key: JBAS-7842  (was: EJBTHREE-2054)
    Component/s: Clustering
                 Web (Tomcat) service
                     (was: Clustering)
                     (was: cache)
       Security: Public


> CLONE -Infinispan replication configuration via @CacheConfig
> ------------------------------------------------------------
>
>                 Key: JBAS-7842
>                 URL: https://jira.jboss.org/jira/browse/JBAS-7842
>             Project: JBoss Application Server
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: Clustering, Web (Tomcat) service
>            Reporter: Brian Stansberry
>             Fix For: JBossAS-6.0.0.M4
>
>
> Make the typical distributed cache configurations configurable via @CacheConfig or jboss.xml; don't force users to go to a separate Infinispan configuration file.
> The typical configurations are:
> 1) synchronous or async (perhaps a better term? async == fire and forget)
> 2) total replication or not?
> 3) if "not", number of backup copies.
> Potentially 2 and 3 could be combined into a numbackups param:
> -1 == total replication (i.e. unlimited)
> 0 == cache is in local mode
> > 0 = DIST w/ numbackups + 1 copies.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira