<?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>DeepakGaikwad.net &#187; Best Practices</title>
	<atom:link href="http://www.deepakgaikwad.net/index.php/tag/best-practices/feed" rel="self" type="application/rss+xml" />
	<link>http://www.deepakgaikwad.net</link>
	<description>Travel Articles and Tech Notes</description>
	<lastBuildDate>Thu, 19 Jan 2012 09:18:45 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Revised Jsp Best Practices</title>
		<link>http://www.deepakgaikwad.net/index.php/2009/11/17/revised-jsp-best-practices.html</link>
		<comments>http://www.deepakgaikwad.net/index.php/2009/11/17/revised-jsp-best-practices.html#comments</comments>
		<pubDate>Tue, 17 Nov 2009 18:10:51 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Jsp]]></category>
		<category><![CDATA[Best Practices]]></category>
		<category><![CDATA[Open Source]]></category>

		<guid isPermaLink="false">http://www.deepakgaikwad.net/?p=981</guid>
		<description><![CDATA[JSPs are an integral part of a web application. If jsps are not coded properly, then it becomes a most unorganized piece of code. You must have seen huge jsps, which end up as a source of defects, and asking you to change them many times. Maintaining such code becomes a very expensive activity. Also it impacts stability of entire application. Following few simple practices can change working on jsp into a happy activity.
1. Reuse Common HTML
There are two main advantages of it. First is &#8211; you are maximising reuse ...]]></description>
		<wfw:commentRss>http://www.deepakgaikwad.net/index.php/2009/11/17/revised-jsp-best-practices.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Important Practical Tips for JUnit Users</title>
		<link>http://www.deepakgaikwad.net/index.php/2009/10/21/practicaljunittips.html</link>
		<comments>http://www.deepakgaikwad.net/index.php/2009/10/21/practicaljunittips.html#comments</comments>
		<pubDate>Wed, 21 Oct 2009 06:06:20 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[JUnit]]></category>
		<category><![CDATA[Tech Notes]]></category>
		<category><![CDATA[Best Practices]]></category>
		<category><![CDATA[Dos and Don'ts]]></category>
		<category><![CDATA[Java]]></category>
		<category><![CDATA[Mocking]]></category>
		<category><![CDATA[Test case]]></category>
		<category><![CDATA[Test Suite]]></category>
		<category><![CDATA[Tips]]></category>

		<guid isPermaLink="false">http://www.deepakgaikwad.net/?p=954</guid>
		<description><![CDATA[Test driven development, automated testing, open source unit testing frameworks, mocking test data, etc. etc. have been buzzing around us for past few years. Most of the Java developers must have used JUnit to write unit test cases at least once. Below are some of the points that I found important while writing JUnit test cases in application development. You can call these as tips, best practices, or whatever you like.

Externalize      Data: Move test data out of test classes. You can have helper classes  ...]]></description>
		<wfw:commentRss>http://www.deepakgaikwad.net/index.php/2009/10/21/practicaljunittips.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

