<?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: SpringOne2gx 2009 Post Mortem</title>
	<atom:link href="http://chrisdail.com/2009/10/24/springone2gx-2009-post-mortem/feed/" rel="self" type="application/rss+xml" />
	<link>http://chrisdail.com/2009/10/24/springone2gx-2009-post-mortem/</link>
	<description>Writing simple, clear and readable code.</description>
	<lastBuildDate>Fri, 11 Jun 2010 13:48:38 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Mark Fisher</title>
		<link>http://chrisdail.com/2009/10/24/springone2gx-2009-post-mortem/comment-page-1/#comment-499</link>
		<dc:creator>Mark Fisher</dc:creator>
		<pubDate>Sun, 25 Oct 2009 00:41:02 +0000</pubDate>
		<guid isPermaLink="false">http://chrisdail.com/?p=65#comment-499</guid>
		<description>I&#039;m glad you enjoyed the conference, and this is a great overview! I just wanted to mention that Spring Integration does support a number of cross-VM transports (JMS, HTTP, etc.) through Channel Adapters and Gateways. As far as the OSGi support, the next milestone release will make all the internal details you saw in that session completely transparent (just add a bundle). We have heard of cases where ESB-based solutions have been refactored to use Spring Integration instead, and the developers were quite happy with the result: less code, less config, and less cost.</description>
		<content:encoded><![CDATA[<p>I&#8217;m glad you enjoyed the conference, and this is a great overview! I just wanted to mention that Spring Integration does support a number of cross-VM transports (JMS, HTTP, etc.) through Channel Adapters and Gateways. As far as the OSGi support, the next milestone release will make all the internal details you saw in that session completely transparent (just add a bundle). We have heard of cases where ESB-based solutions have been refactored to use Spring Integration instead, and the developers were quite happy with the result: less code, less config, and less cost.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Niko &#38; Java &#187; SpringOne 2GX 2009: Link collection</title>
		<link>http://chrisdail.com/2009/10/24/springone2gx-2009-post-mortem/comment-page-1/#comment-498</link>
		<dc:creator>Niko &#38; Java &#187; SpringOne 2GX 2009: Link collection</dc:creator>
		<pubDate>Sat, 24 Oct 2009 20:51:51 +0000</pubDate>
		<guid isPermaLink="false">http://chrisdail.com/?p=65#comment-498</guid>
		<description>[...] all conference coverage: Post Mortem by Chris Dail (with some impressions when to use Roo vs. [...]</description>
		<content:encoded><![CDATA[<p>[...] all conference coverage: Post Mortem by Chris Dail (with some impressions when to use Roo vs. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
