[jboss-jira] [JBoss JIRA] Commented: (AS7-1496) allow ad-hoc config parameters for transaction system

[Stefano Maestri (JIRA)]

    [ https://issues.jboss.org/browse/AS7-1496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12629228#comment-12629228 ] 

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

> allow ad-hoc config parameters for transaction system
> -----------------------------------------------------
>
>                 Key: AS7-1496
>                 URL: https://issues.jboss.org/browse/AS7-1496
>             Project: Application Server 7
>          Issue Type: Feature Request
>          Components: Transactions
>    Affects Versions: 7.0.0.Final
>            Reporter: Jonathan Halliday
>            Assignee: Stefano Maestri
>             Fix For: 7.1.0.Beta1
>
>
> The AS config model currently exposes around a dozen config properties for the transaction system, out of a possible set of over 100 in JBossTS.  Most of the others don't normally need to be changed, but there are exceptions to every rule. To support these edge cases the configuration system should allow additional properties to be specified. This is currently possible by setting system properties before starting the jvm, but not through the server's own config system. The jboss-as-txn schema should be extended to support a <properties> section that can be used in preference to system properties for overriding config values that are not individually exposed.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira