Brian Stansberry wrote:
1) Admin uses tool that communicates with DC to see current configuration of running domain. That means all the default values a) have to be present in the in-memory domain model so they can be displayed and b) have to be present in the in-memory domain model on the server acting as the DC.
So a) means the
components which are (a) managed and (b) are in use but were not specified in the domain.xml
must be provided with an SPI via which they can publish the defaults back to the domain model. Not the end of the world.
But b) is more problematic. We could say the DC has access to all domain resources and can therefore start the components needed by any ServerGroup configuration and thereby determine the defaults. But... yuck. IMHO we should try really hard to avoid imposing any such requirement on the DC.
Blah.
OK how about this alternative view. Things not specified in domain.xml are also not specified in the doman DB, and the host defaults take over, and there's no writing back to the domain database of defaults.
So the total domain view is really the sum of the local host configuration plus the domain configuration at the end of the day.