<?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"
	>
<channel>
	<title>Comments on: Spring flowers</title>
	<atom:link href="http://stage.vambenepe.com/archives/150/feed" rel="self" type="application/rss+xml" />
	<link>http://stage.vambenepe.com/archives/150</link>
	<description>IT management in a changing IT world</description>
	<pubDate>Tue, 19 Aug 2008 22:40:13 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: William Louth</title>
		<link>http://stage.vambenepe.com/archives/150#comment-31382</link>
		<dc:creator>William Louth</dc:creator>
		<pubDate>Thu, 24 Jan 2008 22:51:00 +0000</pubDate>
		<guid isPermaLink="false">http://stage.vambenepe.com/archives/150#comment-31382</guid>
		<description>Eventually the market will force standardization to ensure the multitude of products using such a popular framework do not break each other and that resource management is much more efficient especially for exotic runtimes. The core principles and concepts need to be fully supported within the JVM runtime to achieve this on a realistic scale across different products and up and down the stack and not just within web applications as spring is used most commonly today. There is already movements to address this with the WebBeans specification which hopefully will be expanded in scope to address similar requirements outside web applications. Of course the buyout of SpringSource by say Oracle would create an even more immediate need for a standard to be defined and adopted which is something the team has not really publicly engaged in until now with the Java EE profiles.

William</description>
		<content:encoded><![CDATA[<p>Eventually the market will force standardization to ensure the multitude of products using such a popular framework do not break each other and that resource management is much more efficient especially for exotic runtimes. The core principles and concepts need to be fully supported within the JVM runtime to achieve this on a realistic scale across different products and up and down the stack and not just within web applications as spring is used most commonly today. There is already movements to address this with the WebBeans specification which hopefully will be expanded in scope to address similar requirements outside web applications. Of course the buyout of SpringSource by say Oracle would create an even more immediate need for a standard to be defined and adopted which is something the team has not really publicly engaged in until now with the Java EE profiles.</p>
<p>William</p>
]]></content:encoded>
	</item>
</channel>
</rss>
