Hi Brian, See this issue: https://issues.apache.org/jira/browse/JCR-599 for a proposed solution to this, namely to allow inheritance of workspace config from the repository config template.
This supports the use cases where a single database is used to store all workspaces, so there is no point in being able to configure each workspace independently. There's a patch attached to the issue that allows this to be turned on (although it's against an older jackrabbit version, so it's probable it'll need updating to work against the current version). Unfortunately at the time the patch was proposed there was no interest from the community, so it was never committed. Perhaps if you vote for the issue, someone will look at it again? :-) Cheers, Miro
