<?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: J(2)ee, the basics and beyond</title>
	<atom:link href="http://blog.xebia.com/2009/06/30/j2ee-the-basics-and-beyond-starting-threads/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.xebia.com/2009/06/30/j2ee-the-basics-and-beyond-starting-threads/</link>
	<description></description>
	<lastBuildDate>Thu, 18 Mar 2010 13:27:36 +0100</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Sander Hautvast</title>
		<link>http://blog.xebia.com/2009/06/30/j2ee-the-basics-and-beyond-starting-threads/comment-page-1/#comment-91987</link>
		<dc:creator>Sander Hautvast</dc:creator>
		<pubDate>Thu, 02 Jul 2009 07:30:11 +0000</pubDate>
		<guid isPermaLink="false">http://blog.xebia.com/?p=2305#comment-91987</guid>
		<description>Thanks Lars, I´d immediately opt for a standard jee/j2se solution in favour of commonj. Why not expose a juc Executor?</description>
		<content:encoded><![CDATA[<p>Thanks Lars, I´d immediately opt for a standard jee/j2se solution in favour of commonj. Why not expose a juc Executor?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lars Vonk</title>
		<link>http://blog.xebia.com/2009/06/30/j2ee-the-basics-and-beyond-starting-threads/comment-page-1/#comment-91986</link>
		<dc:creator>Lars Vonk</dc:creator>
		<pubDate>Wed, 01 Jul 2009 18:07:01 +0000</pubDate>
		<guid isPermaLink="false">http://blog.xebia.com/?p=2305#comment-91986</guid>
		<description>Maybe it is better that the JEE servers adjust and provide an implementation of the java.util.concurrent api. Than we could have code that run inside and outside a container. Maybe not all functionality commonj provides is in the concurrent api but the Thread stuff certainly is.</description>
		<content:encoded><![CDATA[<p>Maybe it is better that the JEE servers adjust and provide an implementation of the java.util.concurrent api. Than we could have code that run inside and outside a container. Maybe not all functionality commonj provides is in the concurrent api but the Thread stuff certainly is.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Wilfred Springer</title>
		<link>http://blog.xebia.com/2009/06/30/j2ee-the-basics-and-beyond-starting-threads/comment-page-1/#comment-91983</link>
		<dc:creator>Wilfred Springer</dc:creator>
		<pubDate>Wed, 01 Jul 2009 07:01:12 +0000</pubDate>
		<guid isPermaLink="false">http://blog.xebia.com/?p=2305#comment-91983</guid>
		<description>Nice! Are you planning to cover all the programming restrictions in section 21.1.2 of the EJB spec? (Like, how to avoid using java.io, etc.)</description>
		<content:encoded><![CDATA[<p>Nice! Are you planning to cover all the programming restrictions in section 21.1.2 of the EJB spec? (Like, how to avoid using java.io, etc.)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
