"PeterJ" wrote:
Ales hinted that he doesn't have enough to do and that I should post this here. ;-)

Are there any plans to provide a system property that can be used to decide whether to use bootstrap.xml or boostrap-repo.xml? Right now bootstrap.xml is hard-coded and I had to rename the files to use bootstrap-repo.xml. (Also, is it expected that when using boostrap-repo.xml that hot deployment does not work?)

Yes, we should have something, http://jira.jboss.org/jira/browse/JBAS-5760. Note that there already is a ServerConfig.BOOTSTRAP_URL = jboss.bootstrap.url that should be used.

"PeterJ" wrote:

On a related note, why is profile-service.xml not called simply profile.xml? The extension -service.xml is usually associated with JMX, but in this case the file is used with the microcontainer. I know that file naming conventions (e.g., *-service.xml) apply only in the deploy directory, and not in conf, but it can be initially confusing.

Fair enough. The conventions apply to any deployments processed by the deployers, so its the deployers, deploy directories. We might as well be consistent in naming conventions. http://jira.jboss.org/jira/browse/JBAS-5761