Neil McErlean 9e4ccdd053 This checkin provides the non-RM-specific parts of metadata delegation, which are required for the refactor of classified renditions needed for RM-2549. ...

We essentially have two new services, MetadataDelegationService and MetadataDelegationAdminService, along with some spring configuration and content model configuration (this will come in the subsequent RM-specific checkin.)

metadata-delegation-context.xml defines the spring beans that form the Metadata Delegation services.

The DelegationAdminService is used to attach/detach nodes in pairs such that one node can ‘inherit’ some aspect metadata from another node - the ‘delegate’.

The Delegation class is the definition of a type of link - it’s defined by the aspects that it handles and the type of peer association that it uses to link pairs of nodes.

Delegations must be defined as spring beans in the system to be available for use and they are exposed to Java code via the DelegationRegistry class.

Note that chains of delegations (node A -> node B -> node C) are not supported. Any attempt to attach nodes in a way that would lead to a delegation chain is detected and prevented.

The DelegationService is not about the creation and destruction of links, but is about accessing the metadata on a delegate node.



git-svn-id: https://svn.alfresco.com/repos/alfresco-enterprise/modules/recordsmanagement/BRANCHES/classified_renditions@111292 c4b6b30b-aa2e-2d43-bbcb-ca4b014f7261

2015-09-02 12:03:38 +00:00

..

alfresco

This checkin provides the non-RM-specific parts of metadata delegation, which are required for the refactor of classified renditions needed for RM-2549.

2015-09-02 12:03:38 +00:00