Configuration layout

Antidoto defines dynamic bootstrapping of subsystems, as long as all subsystems adhere to a set of naming and location conventions.

Here some thoughts on the usage of ti-core:

• always use a single point of entry for testcases and runtime environments. E.g., Antidoto uses the bootstrap.xml in the test resources folder as central configuration entry point.
• always provide the default runtime scope configuration context for a subsystem, as described in the bootstrapping documentation. When using different configuration files for different contexts, try putting common configuration elements in a separate configuration fragment and let the other files import it. Don't repeat yourself, duplicated config is at least as bad as duplicated code.
• be carefull with the name of the beans in the configuration files, as they are all loaded in the same application context. Use name patterns to avoid collisions.
• define logging options for runtime environment for every subsystem. If providing published test configuration for a subsystem (means having a test scoped context configuration file in the main resources), define test scoped logging options too.