﻿<?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: getItemValueString and Domino 6.5.5 and 7.0 (Show&#8217;n Tell Thursday)</title>
	<atom:link href="http://per.lausten.dk/blog/2006/08/getitemvaluestring-and-domino-655-and.html/feed" rel="self" type="application/rss+xml" />
	<link>http://per.lausten.dk/blog/2006/08/getitemvaluestring-and-domino-655-and.html</link>
	<description>A blog on Lotus Domino, IT Architecture, technology and other IT stuff by Per Henrik Lausten</description>
	<lastBuildDate>Fri, 12 Mar 2010 11:17:29 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Per Henrik Lausten</title>
		<link>http://per.lausten.dk/blog/2006/08/getitemvaluestring-and-domino-655-and.html/comment-page-1#comment-28</link>
		<dc:creator>Per Henrik Lausten</dc:creator>
		<pubDate>Sun, 29 Oct 2006 07:03:00 +0000</pubDate>
		<guid isPermaLink="false">http://per.lausten.dk/blog/?p=72#comment-28</guid>
		<description>Hi Thirukkovalur Ravi, the issue with the getItemValuString was the only problem I experienced with the upgrade.</description>
		<content:encoded><![CDATA[<p>Hi Thirukkovalur Ravi, the issue with the getItemValuString was the only problem I experienced with the upgrade.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Thirukkovalur Ravi</title>
		<link>http://per.lausten.dk/blog/2006/08/getitemvaluestring-and-domino-655-and.html/comment-page-1#comment-27</link>
		<dc:creator>Thirukkovalur Ravi</dc:creator>
		<pubDate>Sat, 28 Oct 2006 07:20:00 +0000</pubDate>
		<guid isPermaLink="false">http://per.lausten.dk/blog/?p=72#comment-27</guid>
		<description>Please post some of the other probles you faced while upgrading.</description>
		<content:encoded><![CDATA[<p>Please post some of the other probles you faced while upgrading.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mikkel Heisterberg</title>
		<link>http://per.lausten.dk/blog/2006/08/getitemvaluestring-and-domino-655-and.html/comment-page-1#comment-23</link>
		<dc:creator>Mikkel Heisterberg</dc:creator>
		<pubDate>Fri, 01 Sep 2006 04:50:00 +0000</pubDate>
		<guid isPermaLink="false">http://per.lausten.dk/blog/?p=72#comment-23</guid>
		<description>Forgot to mention that this is even more the reason to leverage that Java evaluates if-statements by stopping once the first predicate matches. This means you can do the following test on a null string without getting a NPE:&lt;br/&gt;String my_string = null;&lt;br/&gt;if (null == my_string &#124;&#124; 0 == my_string.length()) {&lt;br/&gt;  // do somthing about empty item&lt;br/&gt;}</description>
		<content:encoded><![CDATA[<p>Forgot to mention that this is even more the reason to leverage that Java evaluates if-statements by stopping once the first predicate matches. This means you can do the following test on a null string without getting a NPE:<br />String my_string = null;<br />if (null == my_string || 0 == my_string.length()) {<br />  // do somthing about empty item<br />}</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mikkel Heisterberg</title>
		<link>http://per.lausten.dk/blog/2006/08/getitemvaluestring-and-domino-655-and.html/comment-page-1#comment-22</link>
		<dc:creator>Mikkel Heisterberg</dc:creator>
		<pubDate>Fri, 01 Sep 2006 04:33:00 +0000</pubDate>
		<guid isPermaLink="false">http://per.lausten.dk/blog/?p=72#comment-22</guid>
		<description>Aaarrrgghhh.... Breaking API&#039;s is something that you really shouldn&#039;t do and IBM is doing it. &lt;br/&gt;&lt;br/&gt;Consider how many applications will start to fail in new, inconsistant and &quot;interesting&quot; ways because of this change. The only good thing is that I have found that the return of null for empty items has been very inconsistant. This has causes me at always test for null and for the length of the returned string so I guess most of my code will be okay. &lt;br/&gt;&lt;br/&gt;It&#039;s a real bummer though.</description>
		<content:encoded><![CDATA[<p>Aaarrrgghhh.... Breaking API's is something that you really shouldn't do and IBM is doing it. </p>
<p>Consider how many applications will start to fail in new, inconsistant and "interesting" ways because of this change. The only good thing is that I have found that the return of null for empty items has been very inconsistant. This has causes me at always test for null and for the length of the returned string so I guess most of my code will be okay. </p>
<p>It's a real bummer though.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
