IBM WebSphere Developer Technical Journal, Eliminate caching in service locator implementations in J2EE 1.3
When bad things happen to good applications
From the developerWorks archives
Date archived: January 3, 2017 | First published: October 13, 2004
This article shows how implementations of the Service Locator pattern that include a resource cache can cause code to run incorrectly in J2EE 1.3 and later versions. While the Service Locator pattern itself is still useful, this article will show how caching with this pattern is harmful rather than helpful, why it should be eliminated from service locator implementations, and offer some practical alternatives.
This content is no longer being updated or maintained. The full article is provided "as is" in a PDF file. Given the rapid evolution of technology, some steps and illustrations may have changed.