<?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 +&#160;XWork</title>
	<atom:link href="http://www.magpiebrain.com/blog/2004/02/24/spring-xwork/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.magpiebrain.com/blog/2004/02/24/spring-xwork/</link>
	<description>Sam Newman's blog</description>
	<pubDate>Sun, 12 Oct 2008 07:34:26 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Sam Newman</title>
		<link>http://www.magpiebrain.com/blog/2004/02/24/spring-xwork/#comment-223</link>
		<dc:creator>Sam Newman</dc:creator>
		<pubDate>Wed, 25 Feb 2004 15:46:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.magpiebrain.com/2004/02/24/spring-xwork/#comment-223</guid>
		<description>I don't see how XWork can loose, beyond the fact that it then becomes dependent on Spring itself. At worst the framework maintains is current capabilities - at best it has a more fully featured IoC framework built right in. Much of XWork's internals would disappear, but there is a lot of value in the command framework itself and this would remain.
I'm going to see if I can come up with a working Spring XWork prototype, to at least gauge the amount of work involved.
</description>
		<content:encoded><![CDATA[<p>I don&#8217;t see how XWork can loose, beyond the fact that it then becomes dependent on Spring itself. At worst the framework maintains is current capabilities &#8211; at best it has a more fully featured IoC framework built right in. Much of XWork&#8217;s internals would disappear, but there is a lot of value in the command framework itself and this would remain.<br />
I&#8217;m going to see if I can come up with a working Spring XWork prototype, to at least gauge the amount of work involved.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Juan Murillo</title>
		<link>http://www.magpiebrain.com/blog/2004/02/24/spring-xwork/#comment-222</link>
		<dc:creator>Juan Murillo</dc:creator>
		<pubDate>Wed, 25 Feb 2004 15:04:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.magpiebrain.com/2004/02/24/spring-xwork/#comment-222</guid>
		<description>I just read Jason's post on the entry before this one and realized that I don't know Xwork well enough to know whether it would loose by usign Spring as a base.

It would be very cool to have it work that way though ;)</description>
		<content:encoded><![CDATA[<p>I just read Jason&#8217;s post on the entry before this one and realized that I don&#8217;t know Xwork well enough to know whether it would loose by usign Spring as a base.</p>
<p>It would be very cool to have it work that way though ;)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Juan Murillo</title>
		<link>http://www.magpiebrain.com/blog/2004/02/24/spring-xwork/#comment-221</link>
		<dc:creator>Juan Murillo</dc:creator>
		<pubDate>Wed, 25 Feb 2004 14:58:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.magpiebrain.com/2004/02/24/spring-xwork/#comment-221</guid>
		<description>I tend to wholeheartedly agree with you.  Some parts of Xwork, like interceptors, could be handled by Spring and Xwork actions would benefit from being POJOs, in general it makes good sense.

Whether this happens or not is basically a matter of internal project politics and OpenSymphony goals.  But i root for the addition of a command pattern framework on top of Spring, and Xwork seems to be the best one out there.</description>
		<content:encoded><![CDATA[<p>I tend to wholeheartedly agree with you.  Some parts of Xwork, like interceptors, could be handled by Spring and Xwork actions would benefit from being POJOs, in general it makes good sense.</p>
<p>Whether this happens or not is basically a matter of internal project politics and OpenSymphony goals.  But i root for the addition of a command pattern framework on top of Spring, and Xwork seems to be the best one out there.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
