<?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 for Frank&#039;s Java Development Blog</title>
	<atom:link href="http://javablog.franksalinas.net/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://javablog.franksalinas.net</link>
	<description>Java Enterprise Development &#38; Technology</description>
	<lastBuildDate>Wed, 10 Mar 2010 23:24:13 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on Java Web Services: Getting Started by Helen Neely</title>
		<link>http://javablog.franksalinas.net/2010/03/09/java-web-services-getting-started/comment-page-1/#comment-684</link>
		<dc:creator>Helen Neely</dc:creator>
		<pubDate>Wed, 10 Mar 2010 23:24:13 +0000</pubDate>
		<guid isPermaLink="false">http://javablog.franksalinas.net/?p=640#comment-684</guid>
		<description>Aawesome, this is one of the simplest and complete example of Web services I&#039;ve seen in a long time. Great stuff.</description>
		<content:encoded><![CDATA[<p>Aawesome, this is one of the simplest and complete example of Web services I&#8217;ve seen in a long time. Great stuff.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Java vs. .NET: Job Market and Salary Survey by Yves Guyon</title>
		<link>http://javablog.franksalinas.net/2008/11/22/java-vs-net-job-market-and-salary-survey/comment-page-1/#comment-383</link>
		<dc:creator>Yves Guyon</dc:creator>
		<pubDate>Wed, 03 Feb 2010 19:21:36 +0000</pubDate>
		<guid isPermaLink="false">http://javablog.franksalinas.net/?p=102#comment-383</guid>
		<description>Great article....</description>
		<content:encoded><![CDATA[<p>Great article&#8230;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Java vs. .NET: Job Market and Salary Survey by mike</title>
		<link>http://javablog.franksalinas.net/2008/11/22/java-vs-net-job-market-and-salary-survey/comment-page-1/#comment-344</link>
		<dc:creator>mike</dc:creator>
		<pubDate>Thu, 19 Nov 2009 13:24:18 +0000</pubDate>
		<guid isPermaLink="false">http://javablog.franksalinas.net/?p=102#comment-344</guid>
		<description>This isnt the whole story.  The reason for the lower demand in .Net is your able to find more resources that work with .Net.  Finding a good Java guy who doesnt want a million dollars (one who can actually keep up with .Net development) is nearly impossible.  .Net simply allows faster development and programmers are able to pick it up faster. Visual Studio is the standard and they all know it. Theres 10 flavors of &quot;Java&quot; and 10 development platforms. Splintering is bad.</description>
		<content:encoded><![CDATA[<p>This isnt the whole story.  The reason for the lower demand in .Net is your able to find more resources that work with .Net.  Finding a good Java guy who doesnt want a million dollars (one who can actually keep up with .Net development) is nearly impossible.  .Net simply allows faster development and programmers are able to pick it up faster. Visual Studio is the standard and they all know it. Theres 10 flavors of &#8220;Java&#8221; and 10 development platforms. Splintering is bad.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The EJB Specification, Concurrency, and Batch Processing by Snehal Antani</title>
		<link>http://javablog.franksalinas.net/2009/03/01/the-ejb-specification-concurrency-and-batch-processing/comment-page-1/#comment-314</link>
		<dc:creator>Snehal Antani</dc:creator>
		<pubDate>Sun, 15 Nov 2009 18:39:45 +0000</pubDate>
		<guid isPermaLink="false">http://javablog.franksalinas.net/?p=211#comment-314</guid>
		<description>An interesting design point to consider is that the degree of parallelism should be a point-in-time decision, influenced by the available capacity of the system, service-level agreements (SLA&#039;s) of concurrent workloads (OLTP, Real-Time, etc), approaching deadlines for other batch jobs in execution, and so on. It&#039;s easy for a developer to arbitrarily spin off 10 commonj threads for parallel execution, but 10 threads may be too few or too many given the other workloads in the system. For designing parallel processing for batch, design the application to not care about the degree of parallelization. Shift the burden of assessing the degree of parallelization to the infrastructure, where some external component applies a partitioning algorithm to the job, dispatches the many instances of the job across the collection of application server threads, where each job instance operates on its own segment of the data. This is how we designed it in WebSphere Compute Grid, IBM&#039;s batch processing technology.

The following article and presentation discuss batch application design patterns. They are generally technology agnostic, though the examples are provided in the context of WebSphere Compute Grid.

- Batch application design:
- http://sites.google.com/site/snehalantani/designingBatchApps.zip
- http://sites.google.com/site/snehalantani/DesigningBatchApplications.pdf

Batch processing infrastructure overview: 
- http://sites.google.com/site/snehalantani/WebSphereDataIntensiveApps.pdf
- http://www-128.ibm.com/developerworks/websphere/techjournal/0804_antani/0804_antani.html

Customer experience with modern batch processing: 
- http://www-01.ibm.com/software/tivoli/features/ccr2/ccr2-2008-12/swissre-websphere-compute-grid-zos.html

Latest Compute Grid overview presentation: 
- http://sites.google.com/site/snehalantani/latestpresentationmaterial</description>
		<content:encoded><![CDATA[<p>An interesting design point to consider is that the degree of parallelism should be a point-in-time decision, influenced by the available capacity of the system, service-level agreements (SLA&#8217;s) of concurrent workloads (OLTP, Real-Time, etc), approaching deadlines for other batch jobs in execution, and so on. It&#8217;s easy for a developer to arbitrarily spin off 10 commonj threads for parallel execution, but 10 threads may be too few or too many given the other workloads in the system. For designing parallel processing for batch, design the application to not care about the degree of parallelization. Shift the burden of assessing the degree of parallelization to the infrastructure, where some external component applies a partitioning algorithm to the job, dispatches the many instances of the job across the collection of application server threads, where each job instance operates on its own segment of the data. This is how we designed it in WebSphere Compute Grid, IBM&#8217;s batch processing technology.</p>
<p>The following article and presentation discuss batch application design patterns. They are generally technology agnostic, though the examples are provided in the context of WebSphere Compute Grid.</p>
<p>- Batch application design:<br />
- <a href="http://sites.google.com/site/snehalantani/designingBatchApps.zip" rel="nofollow">http://sites.google.com/site/snehalantani/designingBatchApps.zip</a><br />
- <a href="http://sites.google.com/site/snehalantani/DesigningBatchApplications.pdf" rel="nofollow">http://sites.google.com/site/snehalantani/DesigningBatchApplications.pdf</a></p>
<p>Batch processing infrastructure overview:<br />
- <a href="http://sites.google.com/site/snehalantani/WebSphereDataIntensiveApps.pdf" rel="nofollow">http://sites.google.com/site/snehalantani/WebSphereDataIntensiveApps.pdf</a><br />
- <a href="http://www-128.ibm.com/developerworks/websphere/techjournal/0804_antani/0804_antani.html" rel="nofollow">http://www-128.ibm.com/developerworks/websphere/techjournal/0804_antani/0804_antani.html</a></p>
<p>Customer experience with modern batch processing:<br />
- <a href="http://www-01.ibm.com/software/tivoli/features/ccr2/ccr2-2008-12/swissre-websphere-compute-grid-zos.html" rel="nofollow">http://www-01.ibm.com/software/tivoli/features/ccr2/ccr2-2008-12/swissre-websphere-compute-grid-zos.html</a></p>
<p>Latest Compute Grid overview presentation:<br />
- <a href="http://sites.google.com/site/snehalantani/latestpresentationmaterial" rel="nofollow">http://sites.google.com/site/snehalantani/latestpresentationmaterial</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Use final by Frank</title>
		<link>http://javablog.franksalinas.net/2009/10/27/use-final-judiciously/comment-page-1/#comment-308</link>
		<dc:creator>Frank</dc:creator>
		<pubDate>Sun, 08 Nov 2009 16:10:49 +0000</pubDate>
		<guid isPermaLink="false">http://javablog.franksalinas.net/?p=574#comment-308</guid>
		<description>@Peter - I agree. If developers could just forget about the potential performance optimizations final may, or may not, provide and focus on the intended purpose of the keyword for preserving immutability code quality would increase. In my opinion, code quality comes before performance and leveraging defensive programming techniques such as enforcing immutabilty appropriately increases code quality.</description>
		<content:encoded><![CDATA[<p>@Peter &#8211; I agree. If developers could just forget about the potential performance optimizations final may, or may not, provide and focus on the intended purpose of the keyword for preserving immutability code quality would increase. In my opinion, code quality comes before performance and leveraging defensive programming techniques such as enforcing immutabilty appropriately increases code quality.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Use final by Peter Lawrey</title>
		<link>http://javablog.franksalinas.net/2009/10/27/use-final-judiciously/comment-page-1/#comment-307</link>
		<dc:creator>Peter Lawrey</dc:creator>
		<pubDate>Sat, 07 Nov 2009 08:47:41 +0000</pubDate>
		<guid isPermaLink="false">http://javablog.franksalinas.net/?p=574#comment-307</guid>
		<description>Its so under utilised, its a shame that final wasn&#039;t the default and a keyword like &#039;var&#039; wasn&#039;t used for mutable variables/fields.

I suggest you make all fields final if possible. While performance is a consideration, I believe it makes it much clearer which fields can be changed over the life of an object.</description>
		<content:encoded><![CDATA[<p>Its so under utilised, its a shame that final wasn&#8217;t the default and a keyword like &#8216;var&#8217; wasn&#8217;t used for mutable variables/fields.</p>
<p>I suggest you make all fields final if possible. While performance is a consideration, I believe it makes it much clearer which fields can be changed over the life of an object.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Five Essential Skills For Software Developers by Frank Robbins</title>
		<link>http://javablog.franksalinas.net/2009/05/09/five-essential-skills-for-software-developers/comment-page-1/#comment-305</link>
		<dc:creator>Frank Robbins</dc:creator>
		<pubDate>Thu, 08 Oct 2009 18:41:17 +0000</pubDate>
		<guid isPermaLink="false">http://javablog.franksalinas.net/?p=343#comment-305</guid>
		<description>Nice article.  I must agree with all the points given. </description>
		<content:encoded><![CDATA[<p>Nice article.  I must agree with all the points given. </p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Java vs. .NET: Job Market and Salary Survey by Joe</title>
		<link>http://javablog.franksalinas.net/2008/11/22/java-vs-net-job-market-and-salary-survey/comment-page-1/#comment-218</link>
		<dc:creator>Joe</dc:creator>
		<pubDate>Tue, 09 Jun 2009 15:03:49 +0000</pubDate>
		<guid isPermaLink="false">http://javablog.franksalinas.net/?p=102#comment-218</guid>
		<description>Important to note that this is in San Fran, which is the backyard for Java.  Makes me wonder if .Net would be on top in other cities.</description>
		<content:encoded><![CDATA[<p>Important to note that this is in San Fran, which is the backyard for Java.  Makes me wonder if .Net would be on top in other cities.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Web Services on JBoss by Frank</title>
		<link>http://javablog.franksalinas.net/2008/10/29/web-services-on-jboss/comment-page-1/#comment-10</link>
		<dc:creator>Frank</dc:creator>
		<pubDate>Mon, 08 Dec 2008 21:26:40 +0000</pubDate>
		<guid isPermaLink="false">http://javablog.franksalinas.net/?p=45#comment-10</guid>
		<description>That doesn&#039;t make sense to me either. Oh well, glad you got it working!</description>
		<content:encoded><![CDATA[<p>That doesn&#8217;t make sense to me either. Oh well, glad you got it working!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Web Services on JBoss by Deon</title>
		<link>http://javablog.franksalinas.net/2008/10/29/web-services-on-jboss/comment-page-1/#comment-9</link>
		<dc:creator>Deon</dc:creator>
		<pubDate>Mon, 08 Dec 2008 04:57:28 +0000</pubDate>
		<guid isPermaLink="false">http://javablog.franksalinas.net/?p=45#comment-9</guid>
		<description>Thanks! I did get it to work, but the only way to get it to work was to make the contextRoot  different for each service. 

@WebContext(contextRoot=&quot;service1&quot;)

@WebContext(contextRoot=&quot;service2&quot;)

This does not make any sense to me. I am not sure why this would work. But it does!

Thanks Again!</description>
		<content:encoded><![CDATA[<p>Thanks! I did get it to work, but the only way to get it to work was to make the contextRoot  different for each service. </p>
<p>@WebContext(contextRoot=&#8221;service1&#8243;)</p>
<p>@WebContext(contextRoot=&#8221;service2&#8243;)</p>
<p>This does not make any sense to me. I am not sure why this would work. But it does!</p>
<p>Thanks Again!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
