<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Avoid Non-Lazy Relationships in Hibernate</title>
	<atom:link href="http://www.basilv.com/psd/blog/2008/avoid-non-lazy-relationships-in-hibernate/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.basilv.com/psd/blog/2008/avoid-non-lazy-relationships-in-hibernate</link>
	<description></description>
	<lastBuildDate>Wed, 08 Feb 2012 03:57:22 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
	<item>
		<title>By: prashant</title>
		<link>http://www.basilv.com/psd/blog/2008/avoid-non-lazy-relationships-in-hibernate/comment-page-1#comment-52155</link>
		<dc:creator>prashant</dc:creator>
		<pubDate>Thu, 22 May 2008 20:09:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.basilv.com/psd/blog/2008/avoid-non-lazy-relationships-in-hibernate#comment-52155</guid>
		<description>The other option is to still use a lazy relationship with OSIV pattern so that the hibernate session is closed on the client side. This will help us not to instantiate the objects on the server but client can decide it on what objects it wants to use.</description>
		<content:encoded><![CDATA[<p>The other option is to still use a lazy relationship with OSIV pattern so that the hibernate session is closed on the client side. This will help us not to instantiate the objects on the server but client can decide it on what objects it wants to use.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Basil Vandegriend</title>
		<link>http://www.basilv.com/psd/blog/2008/avoid-non-lazy-relationships-in-hibernate/comment-page-1#comment-49471</link>
		<dc:creator>Basil Vandegriend</dc:creator>
		<pubDate>Sat, 19 Apr 2008 20:34:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.basilv.com/psd/blog/2008/avoid-non-lazy-relationships-in-hibernate#comment-49471</guid>
		<description>Good question. You can still use a lazy relationship - you just need to instantiate it on the server before sending the objects to the client. Forgetting to do this instantiation can  be a source of errors, but I still think the other benefits of lazy relationships beat out this one isolated negative.</description>
		<content:encoded><![CDATA[<p>Good question. You can still use a lazy relationship &#8211; you just need to instantiate it on the server before sending the objects to the client. Forgetting to do this instantiation can  be a source of errors, but I still think the other benefits of lazy relationships beat out this one isolated negative.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Martin</title>
		<link>http://www.basilv.com/psd/blog/2008/avoid-non-lazy-relationships-in-hibernate/comment-page-1#comment-49404</link>
		<dc:creator>Martin</dc:creator>
		<pubDate>Fri, 18 Apr 2008 15:32:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.basilv.com/psd/blog/2008/avoid-non-lazy-relationships-in-hibernate#comment-49404</guid>
		<description>When you are sending objects to a remote client application, you can&#039;t use lazy relationships if you actually need the data in the client. Don&#039;t you think that&#039;s a pretty common case where you can&#039;t use a lazy relationship?</description>
		<content:encoded><![CDATA[<p>When you are sending objects to a remote client application, you can&#8217;t use lazy relationships if you actually need the data in the client. Don&#8217;t you think that&#8217;s a pretty common case where you can&#8217;t use a lazy relationship?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

