Infrastructure

At the moment Metacat's MN implementation is handled entirely by CrudService, and the CN implementation thus far is handled by CNCoreImpl. The implementation should be modularized to reflect the MN and CN service levels:

From IRC and scratchpad with Ben:

abstract class MNBase {}
MNCoreImpl extends MNBase implements MNCore
MNReadImpl extends MNBase implements MNRead
MNAuthorizationImpl extends MNBase implements MNAuthorization
MNStorageImpl extends MNBase implements MNStorage
MNReplicationImpl extends MNBase implements MNReplication
abstract class CNBase {}
CNCoreImpl extends CNBase implements CNCore
-partial Metacat implementation
CNReadImpl extends CNBase implements CNRead
-all Metacat?
CNAuthorizationImpl extends CNBase implements CNAuthorization
-all Metacat (sysMeta)
**CNIdentityImpl extends CNBase implements CNIdentity
-implemented outside of Metacat
**CNRegisterImpl extends CNBase implements CNRegister
-implemented outside Metacat
CNReplicationImpl extends CNBase implements CNReplication
-proxies to Metacat

• many existing methods in CrudService refactored to MNBase
• sysMeta-related methods in IdentityManager moved to SystemMetadataManager
• similar CN and MN methods will reuse classes/methods for that shared function (e.g., SystemMetadataManager.getInstance().getSystemMetadata()) rather than sharing the root of a class hierarchy for shared methods. We want to keep the distinction between CN and MN stacks very clear at least in the class hierarchy.
• refactor ResourceHandler to minimize duplicate code when handling the REST calls
• Metacat won't implement CNIdentity, CNRegister