Details
-
Sub-task
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
It looks like AttributesMutator.setCacheListener is currently only called from test code. All of these calls can be replaced with AttributesMutator.initCacheListeners with an array of one listener.
It is probably not safe to use AttributesMutator.addCacheListener since it leaves an original listeners in place.
The method is called in about 25 different tests.
Attachments
Issue Links
- links to