[jboss-jira] [JBoss JIRA] (WFLY-4562) Deprecate Infinispan container/cache start mode

[Paul Ferraro (JIRA)]

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

Paul Ferraro updated WFLY-4562:
-------------------------------
    Description: 
start="EAGER" was only added to the Infinispan subsystem for use by JDG - so that a given container or cache service would install as ACTIVE rather than ON_DEMAND.  In the context of WildFly, we would never want this since the modules referenced by cache entries may not yet be loaded.  Many users configure start="EAGER" and inevitably have issues during redeploy. Consequently, we should drop this from the subsystem XSD altogether and deprecate it from the model.
Effectively, only start="LAZY" will be supported.

  was:
start="EAGER" was only added to the Infinispan subsystem for use by JDG - so that a given container or cache service would install as ACTIVE rather than ON_DEMAND.  In the context of WildFly, we would never want this since the modules referenced by cache entries may not yet be loaded.  Consequently, we should drop this from the subsystem XSD altogether and deprecate it from the model.
Effectively, only start="EAGER" will be supported.



> Deprecate Infinispan container/cache start mode
> -----------------------------------------------
>
>                 Key: WFLY-4562
>                 URL: https://issues.jboss.org/browse/WFLY-4562
>             Project: WildFly
>          Issue Type: Enhancement
>          Components: Clustering
>    Affects Versions: 9.0.0.Beta2
>            Reporter: Paul Ferraro
>            Assignee: Paul Ferraro
>             Fix For: 9.0.0.CR1
>
>
> start="EAGER" was only added to the Infinispan subsystem for use by JDG - so that a given container or cache service would install as ACTIVE rather than ON_DEMAND.  In the context of WildFly, we would never want this since the modules referenced by cache entries may not yet be loaded.  Many users configure start="EAGER" and inevitably have issues during redeploy. Consequently, we should drop this from the subsystem XSD altogether and deprecate it from the model.
> Effectively, only start="LAZY" will be supported.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)