<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>spiros.blog() &#187; caching</title>
	<atom:link href="http://www.tzavellas.com/techblog/tag/caching/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.tzavellas.com/techblog</link>
	<description>Spiros Tzavellas’s blog, mostly on software development and Java.</description>
	<lastBuildDate>Fri, 24 Sep 2010 07:42:49 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>Caching in Service Locator implementations</title>
		<link>http://www.tzavellas.com/techblog/2005/06/26/caching-in-service-locator-implementations/</link>
		<comments>http://www.tzavellas.com/techblog/2005/06/26/caching-in-service-locator-implementations/#comments</comments>
		<pubDate>Sun, 26 Jun 2005 18:50:19 +0000</pubDate>
		<dc:creator>spiros</dc:creator>
				<category><![CDATA[Java]]></category>
		<category><![CDATA[caching]]></category>
		<category><![CDATA[design patterns]]></category>
		<category><![CDATA[ejb]]></category>

		<guid isPermaLink="false">http://www.tzavellas.com/techblog/?p=15</guid>
		<description><![CDATA[Here you can find an article by Bobby Woolf that describes why caching inside a Service Locator in J2EE 1.3 applications may have unexpected behavior. The article also provides a nice explanation of the EJB resource reference mechanism. Update (19/9/2005): BTW this is why the Adventure Builder (the sample application developed by SUN for J2EE [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://www-128.ibm.com/developerworks/websphere/techjournal/0410_woolf/0410_woolf.html">Here</a> you can find an article by <a href="http://www-128.ibm.com/developerworks/blogs/dw_blog.jspa?blog=392">Bobby Woolf</a> that describes why caching inside a <a href="http://java.sun.com/blueprints/corej2eepatterns/Patterns/ServiceLocator.html">Service Locator</a> in <a href="http://java.sun.com/j2ee/1.3/index.jsp">J2EE 1.3</a> applications may have unexpected behavior.</p>
<p>The <a href="http://www-128.ibm.com/developerworks/websphere/techjournal/0410_woolf/0410_woolf.html">article</a> also provides a nice explanation of the <a href="http://java.sun.com/products/ejb/">EJB</a> resource reference mechanism.</p>
<p><strong>Update</strong> (19/9/2005):</p>
<p>BTW this is why the <a href="https://adventurebuilder.dev.java.net/">Adventure Builder</a> (the sample application developed by <a href="http://www.sun.com/">SUN</a> for <a href="http://java.sun.com/j2ee/1.4/index.jsp">J2EE 1.4</a>) has two implementations for the <a href="http://java.sun.com/blueprints/corej2eepatterns/Patterns/ServiceLocator.html">Service Locator</a> design pattern.</p>
<p>The <a href="https://adventurebuilder.dev.java.net/source/browse/adventurebuilder/ws/components/servicelocator/src/java/com/sun/j2ee/blueprints/servicelocator/ejb/ServiceLocator.java?rev=1.3&#038;view=markup">first</a> implementation is for the EJB tier and does not have caching to avoid the problem explained in the <a href="ttp://www-128.ibm.com/developerworks/websphere/techjournal/0410_woolf/0410_woolf.html">article</a>.</p>
<p>The <a href="https://adventurebuilder.dev.java.net/source/browse/adventurebuilder/ws/components/servicelocator/src/java/com/sun/j2ee/blueprints/servicelocator/web/ServiceLocator.java?rev=1.4&#038;view=markup">second</a> implementation is for the web tier and uses caching since resource references in the web tier are the per web application and it is safe to cache them in a static variable.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.tzavellas.com/techblog/2005/06/26/caching-in-service-locator-implementations/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

