Details
-
Task
-
Resolution: Done
-
Major
-
12.0.0.Beta1
-
None
Description
See:
Basically, in order to deal with the possibility of override registrations, calls to an MRR typically result in it internally working up to the root of the MRR tree and then walking back down to the target address. So this:
ImmutableManagementResourceRegistration registration = context.getResourceRegistrationFromRoot(address); AttributeDefinition definition = registration.getAttributeAccess(PathAddress.EMPTY_ADDRESS, attributeName).getAttributeDefinition();
is less efficient than:
ImmutableManagementResourceRegistration registration = context.getResourceRegistrationFromRoot(PathAddress.EMPTY_ADDRESS); AttributeDefinition definition = registration.getAttributeAccess(address, attributeName).getAttributeDefinition();
Attachments
Issue Links
- is cloned by
-
WFCORE-4941 Optimize MMR logic within DiscardAttributeChecker.DEFAULT_VALUE
- Closed