[ https://issues.jboss.org/browse/ISPN-1138?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-1138: ----------------------------------- Fix Version/s: 5.0.0.CR4 Description: The following test fails on the last assertion: {code}@Test public void invocationBatching() { System.out.println(org.infinispan.Version.printVersion()); EmbeddedCacheManager manager = new DefaultCacheManager(new GlobalConfiguration(), new Configuration()); Configuration override = new Configuration(); override.fluent().invocationBatching(); assert override.isInvocationBatchingEnabled(); assert manager.defineConfiguration("test1", override).isInvocationBatchingEnabled(); Configuration config = new Configuration(); config.applyOverrides(override); assert config.isInvocationBatchingEnabled(); assert manager.defineConfiguration("test2", config).isInvocationBatchingEnabled(); }{code} In the above code, the last assertion fails. If you modify the above code to test for isIndexingEnabled(), the same failure occurs. The problem is likely generalizable to all boolean configuration properties. was: The following test fails on the last assertion: @Test public void invocationBatching() { System.out.println(org.infinispan.Version.printVersion()); EmbeddedCacheManager manager = new DefaultCacheManager(new GlobalConfiguration(), new Configuration()); Configuration override = new Configuration(); override.fluent().invocationBatching(); assert override.isInvocationBatchingEnabled(); assert manager.defineConfiguration("test1", override).isInvocationBatchingEnabled(); Configuration config = new Configuration(); config.applyOverrides(override); assert config.isInvocationBatchingEnabled(); assert manager.defineConfiguration("test2", config).isInvocationBatchingEnabled(); } In the above code, the last assertion fails. If you modify the above code to test for isIndexingEnabled(), the same failure occurs. The problem is likely generalizable to all boolean configuration properties. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/ISPN-1138?page=com.atlassian.jira.plugin.... ] Galder Zamarreño updated ISPN-1138: ----------------------------------- Workaround Description: Paul, the same thing can be achieved with: {code}Configuration override = new Configuration(); override.fluent().invocationBatching(); assert override.isInvocationBatchingEnabled(); assert cm.defineConfiguration("test1", override).isInvocationBatchingEnabled(); assert cm.defineConfiguration("test2", "test1", new Configuration()).isInvocationBatchingEnabled();{code} Where you take an existing configuration and create a brand new one out of it without any overrides. Workaround: [Workaround Exists] -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/ISPN-1138?page=com.atlassian.jira.plugin.... ] Galder Zamarreño commented on ISPN-1138: ---------------------------------------- Tbh, I have doubts that this applyOverrides() usage should be allowed here, since the overloaded defineConfiguration() is there precisely for this type of use cases where you wanna create a configuration out of a non-default one. In fact, I don't think that users should be able to see applyOverrides() but it's used within other org.infinispan packages. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/ISPN-1138?page=com.atlassian.jira.plugin.... ] Sanne Grinovero updated ISPN-1138: ---------------------------------- Status: Resolved (was: Pull Request Sent) Resolution: Done -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira