akankshajain18 commented on a change in pull request #24:
URL:
https://github.com/apache/sling-org-apache-sling-resourceresolver/pull/24#discussion_r534997531
##########
File path:
src/main/java/org/apache/sling/resourceresolver/impl/ResourceResolverFactoryActivator.java
##########
@@ -304,6 +305,22 @@ protected void activate(final BundleContext bundleContext,
final ResourceResolve
this.observationPaths[i] = new Path(paths[i]);
}
+ // optimize alias path allow list
+ this.aliasPathAllowList.clear();
Review comment:
Hi @wimsymons
If I use a volatile keyword with any collection, a sonar bug is triggered.
( Non-primitive fields as volatile is not allowed.)
That's why I used 'AtomicReferenceArray' as suggested by the sonar cloud.
Later @jsedding and everyone in the review suggested using
copyonwriteArraylist.
Please let me know if there is an issue with copyonwriteArraylist.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
