[ https://issues.jboss.org/browse/AS7-1496?page=com.atlassian.jira.plugin.s... ] Stefano Maestri reassigned AS7-1496: ------------------------------------ Assignee: Stefano Maestri (was: Jonathan Halliday) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-1496?page=com.atlassian.jira.plugin.s... ] Stefano Maestri commented on AS7-1496: -------------------------------------- from the Mailing list: Note that general configuration mechanisms are not allowed in most circumstances. Either a property is important enough to be a first-class part of the schema, or it is not important enough to be a part of the supported configuration. That said, we will allow an unsupported ad-hoc configuration element. The element should be called "extension-properties", and the child elements should be property elements (e.g. <property name="foo" value="bar"/>). Note that unlike our formal schema, ad-hoc properties do NOT have any compatibility or functionality guarantees and are intended as a means by which we can deliver fixes which require configuration outside of the main schema. We can drop support for properties at any time; unrecognized properties are ignored. Here are some guidelines as to when to use what: 1. If the property is something that would be set in the default shipped configuration, it must be a first-class element, not an extension property. 2. If the property is something that is commonly configured or customized, it must be a first-class element, not an extension property. 3. If the property is something that the user should NOT generally be accessing or modifying, it should not be a first-class element. It MAY be added as an extension property as needed later on. I believe that this does mean that we will generally err on the side of having many configuration elements. Also, if we do plan to drop a first-class element, there needs to be a deprecation notice ahead of time; this should be planned well in advance. -- - DML -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/AS7-1496?page=com.atlassian.jira.plugin.s... ] Jason Greene updated AS7-1496: ------------------------------ Fix Version/s: 7.1.0.CR1 (was: 7.1.0.Beta1) Moving all non-critical issues to the CR. If you finish it before we release beta please correct the fix-for version. Thanks -- 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-1496?page=com.atlassian.jira.plugin.s... ] Stefano Maestri resolved AS7-1496. ---------------------------------- Resolution: Done JBossTS rad system properties for this, and they are already manageable from DMR -- 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