[jboss-jira] [JBoss JIRA] (AS7-3549) Make default-cache attribute of cache-container configurable

[Stan Silvert (JIRA)]

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

Stan Silvert resolved AS7-3549.
-------------------------------

    Resolution: Out of Date


Caches can not be created outside of a cache container.  Therefore, if you are creating a new cache container you can not possibly assign a default cache because it is impossible for a member cache to exist.

The reason this started working is because the back end changed to reflect this fact and default cache is no longer a required field when creating a cache container.

The first cache you create for the cache container will automatically be assigned as the default cache.

If you want to assign a different default cache then you create a second cache for the cache container and then check the "Default for cache container?" checkbox. 

I'm still working on the UI for Infinispan.  Please stay tuned.  I know the UI will be far from perfect from a usability standpoint so your feedback will be much appreciated.
                
> Make default-cache attribute of cache-container configurable
> ------------------------------------------------------------
>
>                 Key: AS7-3549
>                 URL: https://issues.jboss.org/browse/AS7-3549
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: Console
>    Affects Versions: 7.1.0.CR1b
>            Reporter: Jan Martiska
>            Assignee: Stan Silvert
>             Fix For: 7.1.1.Final
>
>
> Currently, it is not possible to add a Cache Container using the admin console, cause the form is missing a required attribute 'cache-container':
> JBAS014612: Operation ("add") failed - address: ([
>     ("subsystem" => "infinispan"),
>     ("cache-container" => "fff")
> ]): java.util.NoSuchElementException: No child 'default-cache' exists
> according to AS7-3488 : it seems that default-cache attribute will no longer be required, so this will most likely work again in the future.
> *UPDATE* in the latest snapshot of 2nd February, it seems it already works again
> However, still there should be a form element to input a value for this attribute, it seems like it is not configurable at all (using the console) for the time being.

--
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