At the moment, the InCommon configuration is a little opaque because of the hierarchy of bean definitions used. Many beans are referenced directly, but some are composites pulled from the mdq-server project, which means you need to read the bean definitions there to know what they do. This all dates back to the origin of a lot of these definitions in the UKf tooling, which is pretty monolithic.
We should expand bean references in config.xml until the policy being applied to entities is clear. A good example of this would be standardImportActions.
This doesn't mean putting everything in there, of course; the implementation of the policy should still be one level removed so that it doesn't clutter the configuration at this level.
At the moment, the InCommon configuration is a little opaque because of the hierarchy of bean definitions used. Many beans are referenced directly, but some are composites pulled from the
mdq-serverproject, which means you need to read the bean definitions there to know what they do. This all dates back to the origin of a lot of these definitions in the UKf tooling, which is pretty monolithic.We should expand bean references in
config.xmluntil the policy being applied to entities is clear. A good example of this would bestandardImportActions.This doesn't mean putting everything in there, of course; the implementation of the policy should still be one level removed so that it doesn't clutter the configuration at this level.