David Lloyd wrote:
Brian Stansberry wrote:
Can't/shouldn't these defaults exist in the schema itself?
Maybe in principle, but think of things whose default value might depend on environmental settings (i.e memory size or number of CPUs), or the case where we make a mistake and supply a default which is not reasonable and we have to fix it. The schema is a lot less mutable than our runtime configuration could be.
If the default is a derived from environment settings then we should either expose the non-enviromental portion of the calculation or come up with some other way to express it.
The key thing to me is to not be pulling data from all over the place; the domain configuration needs to be largely self-contained. If we want to say that domain.xml is the end user document and some standarddomain.xml[1] located next to it is the source of defaults, that's ok. Just not a situation like we have now where defaults are coming in from all over the place.
[1] A joke name, reference to the old standardjboss.xml that serves a similar function.