Decoupling

As a developer I'd like to explore to what extent decoupling of GeoNetwork components is possible over the short term and the long term and what that would look like. I think that there are potentially multiple levels of decoupling. At one level is a kind of "maven" artifact level of GeoNetwork libraries. At another is decoupling at the level of more or less self-contained modules that can run independently. Perhaps there are other ways to acheive the same or similar functionality as well. Some motivations are:

1. reuse: a developer can use the same libraries in a customized application
2. sustainability: developers on other projects that use the library or module can contribute back to parts of GeoNetwork without needing an understanding of the whole; it also broadens the GeoNetwork umbrella
3. scalability: modules can be deployed across servers, etc.
4. users may want or need some GeoNetwork components but be required to use proprietary/alternative components for others

Consideration:

• Migrating spring MVC will simplify because config & resources code, etc.. can be in single module
• Wro4j configuration files to be auto-discoverable within a jar or within the webapp
• convention based lookup for the configuration