<?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: Explain the Java Static Modifier</title>
	<atom:link href="http://javapapers.com/core-java/explain-the-java-static-modifier/feed/" rel="self" type="application/rss+xml" />
	<link>http://javapapers.com/core-java/explain-the-java-static-modifier/</link>
	<description>BLOG on core java, servlets, JSP, design patterns interview questions with quality answers, source code and discussions.</description>
	<lastBuildDate>Tue, 07 Sep 2010 14:43:42 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Virat Gandhi</title>
		<link>http://javapapers.com/core-java/explain-the-java-static-modifier/comment-page-1/#comment-1132</link>
		<dc:creator>Virat Gandhi</dc:creator>
		<pubDate>Tue, 30 Mar 2010 08:56:45 +0000</pubDate>
		<guid isPermaLink="false">http://javapapers.com/?p=49#comment-1132</guid>
		<description>hi...!

If you would use static methods and fields only, you would end up programming procedural like you would do with C or Pascal, loosing all the benefits of oop..so static method is used only when required and instance method is used elsewhere to get the benefit of oop.</description>
		<content:encoded><![CDATA[<p>hi&#8230;!</p>
<p>If you would use static methods and fields only, you would end up programming procedural like you would do with C or Pascal, loosing all the benefits of oop..so static method is used only when required and instance method is used elsewhere to get the benefit of oop.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aatish</title>
		<link>http://javapapers.com/core-java/explain-the-java-static-modifier/comment-page-1/#comment-412</link>
		<dc:creator>Aatish</dc:creator>
		<pubDate>Sun, 06 Dec 2009 23:44:01 +0000</pubDate>
		<guid isPermaLink="false">http://javapapers.com/?p=49#comment-412</guid>
		<description>Good, concise answer. 

But, I would want one more thing to be added to it:
Static methods can&#039;t be overridden, which implies they are final methods. Rather, the concept of overridden itself should never arise because static methods are part of a class and not of an object.

But, because of the notation we abuse by writing obj.staticMethod(), people generally get confused.

Thanks,</description>
		<content:encoded><![CDATA[<p>Good, concise answer. </p>
<p>But, I would want one more thing to be added to it:<br />
Static methods can&#8217;t be overridden, which implies they are final methods. Rather, the concept of overridden itself should never arise because static methods are part of a class and not of an object.</p>
<p>But, because of the notation we abuse by writing obj.staticMethod(), people generally get confused.</p>
<p>Thanks,</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: What is a static import in java?</title>
		<link>http://javapapers.com/core-java/explain-the-java-static-modifier/comment-page-1/#comment-295</link>
		<dc:creator>What is a static import in java?</dc:creator>
		<pubDate>Tue, 17 Nov 2009 18:04:27 +0000</pubDate>
		<guid isPermaLink="false">http://javapapers.com/?p=49#comment-295</guid>
		<description>[...] coming to the static import part. Like the above ugly line we have been unknowingly using (abusing) the java static [...]</description>
		<content:encoded><![CDATA[<p>[...] coming to the static import part. Like the above ugly line we have been unknowingly using (abusing) the java static [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
