Brian Stansberry wrote:
David Lloyd wrote:
Perhaps the web container ought to have sensible defaults in the event that no information is specified but web deployments are present. Or perhaps in this event, the default web container definition will automatically be written back to domain.xml?
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.