[jboss-dev-forums] [Management Development] - Profiles in domain.xml

David Lloyd do-not-reply at jboss.com
Wed Jun 2 18:16:00 EDT 2010


David Lloyd [http://community.jboss.org/people/david.lloyd%40jboss.com] replied to the discussion

"Profiles in domain.xml"

To view the discussion, visit: http://community.jboss.org/message/545947#545947

--------------------------------------------------------------
> Brian Stansberry wrote:
> 
> > 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.
I get where you're coming from.  I'd just be concerned though if it got to a point where it is impossible to start up a server without a large and complex domain.xml file.  I don't like the idea of merging XML documents though.  I don't think the defaults would be coming from everyplace, just from components which are (a) managed and (b) are in use but were not specified in the domain.xml.

Another scenario this could be relevant is where a component is upgraded, causing more features to become available.  The component might want to update its domain configuration with the new default values for the new features.  Patching a secondary XML file at upgrade time seems much messier than just using the defaults from a management perspective.

--------------------------------------------------------------

Reply to this message by going to Community
[http://community.jboss.org/message/545947#545947]

Start a new discussion in Management Development at Community
[http://community.jboss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2107]

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jboss-dev-forums/attachments/20100602/7aa48be1/attachment.html 


More information about the jboss-dev-forums mailing list