Code pitfalls code-pitfalls
Avoid Sling Bindings in Java code avoid-sling-bindings-in-java-code
Sling Bindings are an inappropriate way to get access to a service in 90% of cases. Instead, you should use @Reference or @Inject annotations.
Avoid Thread.interrupt in Java code avoid-thread-interrupt-in-java-code
Thread.interrupt is dangerous because it can close files, including Lucene files and persistent cache files, when called at the wrong time.
Avoid mixing Java synchronization with ReadWriteLocks avoid-mixing-java-synchronization-with-readwritelocks
This can lead to a race condition in which the code will eventually deadlock.
recommendation-more-help
19ffd973-7af2-44d0-84b5-d547b0dffee2