Make it possible not to manage merge on ContributionFragmentRegistry
implementations
------------------------------------------------------------------------------------
Key: NXP-7814
URL: https://jira.nuxeo.com/browse/NXP-7814
Project: Nuxeo Enterprise Platform
Issue Type: Improvement
Affects Versions: 5.4.2
Reporter: Anahide Tchertchian
Assignee: Anahide Tchertchian
Fix For: 5.5
ContributionFragmentRegistry implementations support hot reload because they
will handle adding/removal/merge of contributions for complex cases (like
removing the 2nd, not last, override of a given contribution, and return the
merged result when getting the given contribution from the service).
But sometimes the service does not handle merge, it only needs to get the
accurate implementation, also when removing one of the overrides
=> add a hook where you can specify that the contribution registry will not
perform any merge, so that #clone and #merge method will not be called.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
ECM-tickets mailing list
[email protected]
http://lists.nuxeo.com/mailman/listinfo/ecm-tickets
