<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: EE6 Public Draft APPROVED</title>
	<atom:link href="http://sacha.labourey.com/2009/02/26/ee6-public-draft-approved/feed/" rel="self" type="application/rss+xml" />
	<link>http://sacha.labourey.com/2009/02/26/ee6-public-draft-approved/</link>
	<description>Onward!</description>
	<lastBuildDate>Sat, 24 Dec 2011 07:04:36 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Sacha</title>
		<link>http://sacha.labourey.com/2009/02/26/ee6-public-draft-approved/#comment-1146</link>
		<dc:creator><![CDATA[Sacha]]></dc:creator>
		<pubDate>Fri, 27 Feb 2009 12:19:57 +0000</pubDate>
		<guid isPermaLink="false">http://sacha.labourey.com/?p=276#comment-1146</guid>
		<description><![CDATA[OK, thanks for the clarification Pawel, it makes indeed more sense.

cheers,


sacha]]></description>
		<content:encoded><![CDATA[<p>OK, thanks for the clarification Pawel, it makes indeed more sense.</p>
<p>cheers,</p>
<p>sacha</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paweł Paprota</title>
		<link>http://sacha.labourey.com/2009/02/26/ee6-public-draft-approved/#comment-1145</link>
		<dc:creator><![CDATA[Paweł Paprota]]></dc:creator>
		<pubDate>Fri, 27 Feb 2009 11:19:36 +0000</pubDate>
		<guid isPermaLink="false">http://sacha.labourey.com/?p=276#comment-1145</guid>
		<description><![CDATA[Unfortunate wording on my part, sorry! I mean that I am curious on how SpringSource&#039;s involvement worked out in practice. For now I can only judge it by some news items I&#039;ve read during past several months and their vote comment that was surprisingly on merit in contrast to other, often &quot;auto-generated&quot; ones. Although I understand that the comment is only a small part of what JSR execs are doing :-)

In general I would think that SpringSource had a clear &quot;technical agenda&quot; going into the JSR process given their background in enterprise Java product landscape. And it&#039;s the reason I will look closer than usually at JSR process (especially such high profile ones as EE).]]></description>
		<content:encoded><![CDATA[<p>Unfortunate wording on my part, sorry! I mean that I am curious on how SpringSource&#8217;s involvement worked out in practice. For now I can only judge it by some news items I&#8217;ve read during past several months and their vote comment that was surprisingly on merit in contrast to other, often &#8220;auto-generated&#8221; ones. Although I understand that the comment is only a small part of what JSR execs are doing <img src='http://s0.wp.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
<p>In general I would think that SpringSource had a clear &#8220;technical agenda&#8221; going into the JSR process given their background in enterprise Java product landscape. And it&#8217;s the reason I will look closer than usually at JSR process (especially such high profile ones as EE).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sacha</title>
		<link>http://sacha.labourey.com/2009/02/26/ee6-public-draft-approved/#comment-1144</link>
		<dc:creator><![CDATA[Sacha]]></dc:creator>
		<pubDate>Fri, 27 Feb 2009 10:26:49 +0000</pubDate>
		<guid isPermaLink="false">http://sacha.labourey.com/?p=276#comment-1144</guid>
		<description><![CDATA[Pawel,

How can you say, in the same sentence:
i) &quot;SS made a good addition to the JSR process&quot;, and
ii) &quot;I need [...] to judge to what extent they were allowed to influence the outcome&quot;

What do you mean?

I am in favor of making all EE discussions be public, I think it would help the community have more leverage on where things go.]]></description>
		<content:encoded><![CDATA[<p>Pawel,</p>
<p>How can you say, in the same sentence:<br />
i) &#8220;SS made a good addition to the JSR process&#8221;, and<br />
ii) &#8220;I need [...] to judge to what extent they were allowed to influence the outcome&#8221;</p>
<p>What do you mean?</p>
<p>I am in favor of making all EE discussions be public, I think it would help the community have more leverage on where things go.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paweł Paprota</title>
		<link>http://sacha.labourey.com/2009/02/26/ee6-public-draft-approved/#comment-1143</link>
		<dc:creator><![CDATA[Paweł Paprota]]></dc:creator>
		<pubDate>Fri, 27 Feb 2009 09:55:46 +0000</pubDate>
		<guid isPermaLink="false">http://sacha.labourey.com/?p=276#comment-1143</guid>
		<description><![CDATA[It&#039;s nice to see that SpringSource made a good addition to the JSR process. I need to read the spec more closely to judge to what extent they were allowed to influence the outcome.

I must say I am disappointed by Sacha&#039;s comments towards SpringSource&#039;s vote, I am sure they don&#039;t have some evil ultimate domination plan neither they want to undermine JSR efforts. If only everyone could get along technically and politically speaking then it would be so much more productive world...]]></description>
		<content:encoded><![CDATA[<p>It&#8217;s nice to see that SpringSource made a good addition to the JSR process. I need to read the spec more closely to judge to what extent they were allowed to influence the outcome.</p>
<p>I must say I am disappointed by Sacha&#8217;s comments towards SpringSource&#8217;s vote, I am sure they don&#8217;t have some evil ultimate domination plan neither they want to undermine JSR efforts. If only everyone could get along technically and politically speaking then it would be so much more productive world&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sacha</title>
		<link>http://sacha.labourey.com/2009/02/26/ee6-public-draft-approved/#comment-1141</link>
		<dc:creator><![CDATA[Sacha]]></dc:creator>
		<pubDate>Fri, 27 Feb 2009 06:49:06 +0000</pubDate>
		<guid isPermaLink="false">http://sacha.labourey.com/?p=276#comment-1141</guid>
		<description><![CDATA[Hello cdiesse,

We have indeed invested a lot of effort and innovation in EE6 and other specs (299, JSF, EJB, etc.)

I obviously disagree with the order of your preference list. Well, maybe not so much since tomcat is included in JBoss - but with additional services which boost it on steroids :)

Cheers,

sacha]]></description>
		<content:encoded><![CDATA[<p>Hello cdiesse,</p>
<p>We have indeed invested a lot of effort and innovation in EE6 and other specs (299, JSF, EJB, etc.)</p>
<p>I obviously disagree with the order of your preference list. Well, maybe not so much since tomcat is included in JBoss &#8211; but with additional services which boost it on steroids <img src='http://s0.wp.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>Cheers,</p>
<p>sacha</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: cdiesse</title>
		<link>http://sacha.labourey.com/2009/02/26/ee6-public-draft-approved/#comment-1140</link>
		<dc:creator><![CDATA[cdiesse]]></dc:creator>
		<pubDate>Thu, 26 Feb 2009 23:22:46 +0000</pubDate>
		<guid isPermaLink="false">http://sacha.labourey.com/?p=276#comment-1140</guid>
		<description><![CDATA[Good news ! 
For this run, I think jboss has been paid for his involvement, loyalty  and strong support for java EE. Most java developers are waiting the first jsr-299 ri implementation from jboss and the the jsf-2.0 richfaces version.  

The reference open source for Java EE 6 in top preference list are : tomcat 6, glassfish v3 and jboss 5. (Maybe Oracle AS)

Spring must align on sun or die.

My 2 cents.]]></description>
		<content:encoded><![CDATA[<p>Good news !<br />
For this run, I think jboss has been paid for his involvement, loyalty  and strong support for java EE. Most java developers are waiting the first jsr-299 ri implementation from jboss and the the jsf-2.0 richfaces version.  </p>
<p>The reference open source for Java EE 6 in top preference list are : tomcat 6, glassfish v3 and jboss 5. (Maybe Oracle AS)</p>
<p>Spring must align on sun or die.</p>
<p>My 2 cents.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sacha</title>
		<link>http://sacha.labourey.com/2009/02/26/ee6-public-draft-approved/#comment-1138</link>
		<dc:creator><![CDATA[Sacha]]></dc:creator>
		<pubDate>Thu, 26 Feb 2009 21:07:30 +0000</pubDate>
		<guid isPermaLink="false">http://sacha.labourey.com/?p=276#comment-1138</guid>
		<description><![CDATA[Thanks for your comment anil, we value your feedback.]]></description>
		<content:encoded><![CDATA[<p>Thanks for your comment anil, we value your feedback.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: anil</title>
		<link>http://sacha.labourey.com/2009/02/26/ee6-public-draft-approved/#comment-1137</link>
		<dc:creator><![CDATA[anil]]></dc:creator>
		<pubDate>Thu, 26 Feb 2009 20:52:29 +0000</pubDate>
		<guid isPermaLink="false">http://sacha.labourey.com/?p=276#comment-1137</guid>
		<description><![CDATA[even more proof that jboss is still nothing more than a bunch of crybaby wankers. always taking pot-shots anywhere they can instead of just taking the high road.]]></description>
		<content:encoded><![CDATA[<p>even more proof that jboss is still nothing more than a bunch of crybaby wankers. always taking pot-shots anywhere they can instead of just taking the high road.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sacha</title>
		<link>http://sacha.labourey.com/2009/02/26/ee6-public-draft-approved/#comment-1136</link>
		<dc:creator><![CDATA[Sacha]]></dc:creator>
		<pubDate>Thu, 26 Feb 2009 20:49:19 +0000</pubDate>
		<guid isPermaLink="false">http://sacha.labourey.com/?p=276#comment-1136</guid>
		<description><![CDATA[Thanks Adam. FYI, the complete list of all comments made by all EC members is available from my post - third hyperlink.]]></description>
		<content:encoded><![CDATA[<p>Thanks Adam. FYI, the complete list of all comments made by all EC members is available from my post &#8211; third hyperlink.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adam FitzGerald</title>
		<link>http://sacha.labourey.com/2009/02/26/ee6-public-draft-approved/#comment-1135</link>
		<dc:creator><![CDATA[Adam FitzGerald]]></dc:creator>
		<pubDate>Thu, 26 Feb 2009 20:45:14 +0000</pubDate>
		<guid isPermaLink="false">http://sacha.labourey.com/?p=276#comment-1135</guid>
		<description><![CDATA[For the record, here is the complete text of the SpringSource comment regarding EE6 review vote: 

&quot;The introduction of profiles is a step in the right direction. However, we are disappointed not to see a minimal web profile, especially as this has become the choice of most enterprise Java users.

As with previous releases, the inclusion of  unproven technology is a risk, especially in JSR 299 and EJB concurrency annotations. The number of substantial changes late in the process also gives us concern about the maturity of the result--especially, the impact of the scope creep of JSR 299 on other specifications.

Experience has shown that tying dependency injection features to a server environment does not match user requirements, as injection is common to all application types. We would have preferred to see a dependency injection model for SE, as we proposed in 2007.

Finally, we are not convinced that the end result matches the goals of Java EE 6 as defined in the original specification request, which we strongly supported.&quot;

Adam FitzGerald
SpringSource]]></description>
		<content:encoded><![CDATA[<p>For the record, here is the complete text of the SpringSource comment regarding EE6 review vote: </p>
<p>&#8220;The introduction of profiles is a step in the right direction. However, we are disappointed not to see a minimal web profile, especially as this has become the choice of most enterprise Java users.</p>
<p>As with previous releases, the inclusion of  unproven technology is a risk, especially in JSR 299 and EJB concurrency annotations. The number of substantial changes late in the process also gives us concern about the maturity of the result&#8211;especially, the impact of the scope creep of JSR 299 on other specifications.</p>
<p>Experience has shown that tying dependency injection features to a server environment does not match user requirements, as injection is common to all application types. We would have preferred to see a dependency injection model for SE, as we proposed in 2007.</p>
<p>Finally, we are not convinced that the end result matches the goals of Java EE 6 as defined in the original specification request, which we strongly supported.&#8221;</p>
<p>Adam FitzGerald<br />
SpringSource</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: J2EE 6 - Draft - Approved &#171; Java Hellenic User Group</title>
		<link>http://sacha.labourey.com/2009/02/26/ee6-public-draft-approved/#comment-1134</link>
		<dc:creator><![CDATA[J2EE 6 - Draft - Approved &#171; Java Hellenic User Group]]></dc:creator>
		<pubDate>Thu, 26 Feb 2009 15:46:41 +0000</pubDate>
		<guid isPermaLink="false">http://sacha.labourey.com/?p=276#comment-1134</guid>
		<description><![CDATA[[...] εδώ.Σχόλια εδώ. Το διαβάσαμε στο [...]]]></description>
		<content:encoded><![CDATA[<p>[...] εδώ.Σχόλια εδώ. Το διαβάσαμε στο [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

