[jboss-dev-forums] [Design of Management Features on JBoss] - Re: JBAS-6672, null values and defaults

[charles.crouch@jboss.com]

Ok, just to make sure we're all clear on the use cases the console needs to support, I've described them below. The *how* part, is up for more discussion.

1) user doesn't want to specify a particular value for a configuration property, they are happy to take the server default value (which itself may change over time).
So if todays default is 20, we can't store 20 as the value of the property, since tomorrow the default may be 30, and the user has specified that they wish to always take the server default, regardless of what that is.

2) the user wants to specify a particular value for a configuration property. This is the typical scenario, e.g. a user enters in the jndiName for a datasource.

3) user wants to explicitly specify that a value is empty for a configuration property, they don't want to user the server default. For example the server default for "new-connection-sql" on a Datsource could be ";". So if the user leaves that value unset thats what the Datasource will use, however if the user explicitly sets the value to null (or empty string) then they are saying they don't want any SQL run on new connections.

Thanks

View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4221693#4221693

Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4221693