[ https://issues.jboss.org/browse/AS7-4198?page=com.atlassian.jira.plugin.s... ] Paul Ferraro reassigned AS7-4198: --------------------------------- Assignee: Richard Achmatowicz (was: Paul Ferraro) -- 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

[ https://issues.jboss.org/browse/AS7-4198?page=com.atlassian.jira.plugin.s... ] Richard Achmatowicz edited comment on AS7-4198 at 3/26/12 5:56 PM: ------------------------------------------------------------------- The xsd defaults have no effect on processing; they are there for documentation purposes only (according to Brian). All default values are controlled through AttributeDefintions within the subsystem definition. This is primarily because management operations, whether they are specified via XML elements or the management interface, all end up as invoked management operations which access the AttributeDefinitions and their defaults. The xsd defaults were set up to match the defaults used in the attribute definitions. In the case of l1-lifespan, the default is actually 600000. When building the Infinispan configuration from the management model information, if l1-lifespan > 0, l1 caching is turned on. So l1 caching is actually on by default (or at least should be by intention). was (Author: rachmato): The xsd defaults have no effect on processing; they are there for documentation purposes only (according to Brian). All default values are controlled through AttributeDefintions within the subsystem definition. This is primarily because management operations, whether they are specified via XML elements or the management interface, all end up as invoked management operations. The xsd defaults were set up to match the defaults used in the attribute definitions. In the case of l1-lifespan, the default is actually 600000. When building the Infinispan configuration from the management model information, if l1-lifespan > 0, l1 caching is turned on. So l1 caching is actually on by default (or at least should be by intention). -- 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

[ https://issues.jboss.org/browse/AS7-4198?page=com.atlassian.jira.plugin.s... ] Michal Linhard commented on AS7-4198: ------------------------------------- In both JDG 6.0.0.ER4 and Infinispan 5.1.2.Final the L1 Cache is disabled by default, although from the code it might seem differently. See my mail to infinispan-dev: http://lists.jboss.org/pipermail/infinispan-dev/2012-March/010423.html -- 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

[ https://issues.jboss.org/browse/AS7-4198?page=com.atlassian.jira.plugin.s... ] Michal Linhard commented on AS7-4198: ------------------------------------- I know that XSD is not parsed for default values, and that's the point of this JIRA. And not even the code: https://github.com/jbossas/jboss-as/blob/master/clustering/infinispan/src... determines the final outcome of whether L1 is or is not enabled. Because it is only activated when the attribute is _present_. (see the parsing logic) Yes the question is whether we want L1 in ALL caches by default or not. (not some specific ones, it's not relevant to this issue) My opinion is: NO, but that's of course open to a debate. If we choose the default "L1 is NOT enabled" then we should IMO change the values both in schema and the code to 0, so that they don't confuse people. I agree that the name of this JIRA is not optimal. Default value from schema being ignored is an expected thing. -- 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

[ https://issues.jboss.org/browse/AS7-4198?page=com.atlassian.jira.plugin.s... ] Radoslav Husar commented on AS7-4198: ------------------------------------- Look at master for this https://github.com/jbossas/jboss-as as it will be rebased. -- 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

[ https://issues.jboss.org/browse/AS7-4198?page=com.atlassian.jira.plugin.s... ] Paul Ferraro resolved AS7-4198. ------------------------------- Resolution: Duplicate Issue Duplicated by https://issues.jboss.org/browse/AS7-4350 -- 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