[JBoss JIRA] (ISPN-11410) Upgrade console 0.4.Final
by Katia Aresti (Jira)
Katia Aresti created ISPN-11410:
-----------------------------------
Summary: Upgrade console 0.4.Final
Key: ISPN-11410
URL: https://issues.redhat.com/browse/ISPN-11410
Project: Infinispan
Issue Type: Component Upgrade
Components: Console
Affects Versions: 10.1.3.Final
Reporter: Katia Aresti
Assignee: Katia Aresti
upgrade to 0.4.Final
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (ISPN-11409) Integration tests for examples
by Katia Aresti (Jira)
Katia Aresti created ISPN-11409:
-----------------------------------
Summary: Integration tests for examples
Key: ISPN-11409
URL: https://issues.redhat.com/browse/ISPN-11409
Project: Infinispan
Issue Type: Component Upgrade
Components: Quarkus, Spring Integration
Affects Versions: 10.1.3.Final
Reporter: Katia Aresti
Assignee: Katia Aresti
Today Infinispan Server needs to be run or use all the dependencies we have in the test jars to create one programatically.
With the latest infinispan-server and test-containers, add integration tests for Quarkus and Spring-Boot
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (ISPN-11367) getCache(name) should never use the default cache's configuration
by Dan Berindei (Jira)
[ https://issues.redhat.com/browse/ISPN-11367?page=com.atlassian.jira.plugi... ]
Dan Berindei updated ISPN-11367:
--------------------------------
Status: Pull Request Sent (was: Open)
Git Pull Request: https://github.com/infinispan/infinispan/pull/7974
> getCache(name) should never use the default cache's configuration
> -----------------------------------------------------------------
>
> Key: ISPN-11367
> URL: https://issues.redhat.com/browse/ISPN-11367
> Project: Infinispan
> Issue Type: Enhancement
> Components: Configuration, Core
> Affects Versions: 10.1.2.Final, 11.0.0.Alpha1
> Reporter: Dan Berindei
> Assignee: Dan Berindei
> Priority: Major
> Fix For: 11.0.0.Alpha2
>
>
> {{DefaultCacheManager.getCache(name)}} will try to create the cache if it doesn't exist, and if a matching configuration doesn't exist either it uses the default cache's configuration.
> Since 9.0 named cache configurations no longer inherit from the default cache configuration, so using the default cache's configuration as a default configuration is surprising.
> {{DefaultCacheManager.getCache(name)}} should only create the cache if a matching configuration exists, otherwise it should throw an exception.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month