<?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: Moaning about Struts 1 won&#8217;t help you move to Struts 2</title>
	<atom:link href="http://www.firstpartners.net/blog/technology/2007/07/27/moaning-about-struts-1-wont-help-you-move-to-struts-2/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.firstpartners.net/blog/technology/2007/07/27/moaning-about-struts-1-wont-help-you-move-to-struts-2/</link>
	<description>People, Technology, Business and Innovation</description>
	<lastBuildDate>Mon, 15 Feb 2010 20:01:14 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: venkat</title>
		<link>http://www.firstpartners.net/blog/technology/2007/07/27/moaning-about-struts-1-wont-help-you-move-to-struts-2/comment-page-1/#comment-234938</link>
		<dc:creator>venkat</dc:creator>
		<pubDate>Fri, 25 Apr 2008 18:02:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.firstpartners.net/blog/technology/2007/07/27/moaning-about-struts-1-wont-help-you-move-to-struts-2/#comment-234938</guid>
		<description>Struts 1.x is the most aweful, confusing
and ridiculuously difficult technology
the programming world might have 
ever seen. no wonder its mention 
can be found here :

http://www.manageability.org/blog/stuff/most-valuable-personalities-in-java
(Hats off to the author of this article)


what is more pathetic to find is that
there are some people who are for
whatever (personal) reasons are 
promoting this technology. 

2 cents advise is to use Struts 2, JSF, 
Stripes instead of putting thankless 
effort and wasting time in the trench.</description>
		<content:encoded><![CDATA[<p>Struts 1.x is the most aweful, confusing<br />
and ridiculuously difficult technology<br />
the programming world might have<br />
ever seen. no wonder its mention<br />
can be found here :</p>
<p><a href="http://www.manageability.org/blog/stuff/most-valuable-personalities-in-java" onclick="javascript:pageTracker._trackPageview('/outbound/comment/www.manageability.org');" rel="nofollow">http://www.manageability.org/blog/stuff/most-valuable-personalities-in-java</a><br />
(Hats off to the author of this article)</p>
<p>what is more pathetic to find is that<br />
there are some people who are for<br />
whatever (personal) reasons are<br />
promoting this technology. </p>
<p>2 cents advise is to use Struts 2, JSF,<br />
Stripes instead of putting thankless<br />
effort and wasting time in the trench.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: admin</title>
		<link>http://www.firstpartners.net/blog/technology/2007/07/27/moaning-about-struts-1-wont-help-you-move-to-struts-2/comment-page-1/#comment-83923</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Fri, 27 Jul 2007 14:43:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.firstpartners.net/blog/technology/2007/07/27/moaning-about-struts-1-wont-help-you-move-to-struts-2/#comment-83923</guid>
		<description>Bill,

The &#039;moaning&#039; thing came across more harshly than I intended :-) 

I don&#039;t thing Struts 2 is *the* answer, I do think it is a big improvement. To use the bullet points from your original post:

* Verbosity: Better but not perfect. Fewer classes needed, more of them POJO and sensible defaults in the config file.

* Url pattern mapping: Slightly better, if this is a must have , then I&#039;d recommend Spring MVC which is much more power in this area.

* Struts(-config).xml: Better , still suffering for the &#039;one place to do config&#039; - easy to know where to find stuff. Can use includes to split the file  if require.

* Not so difficult to test. Struts 2 is pretty much plain Java all the way - a lot easier to (J)unit test. My single biggest reason to make the move.

* Template support: Agree with you here. Use Sitemesh. Even better, use sitemesh pre configured with Struts2 (using Maven and Appfuse)

* MVC v the Web in general: I suppose it depends on the way that you think. Not matter what your point of view, At least Struts (2) isn&#039;t as bad as JSF.


The underlying the bulk of my comment post: All these are reasons to move from Struts 1 (to framework of your choice). Convincing business users isn&#039;t going to be as easy.

Paul</description>
		<content:encoded><![CDATA[<p>Bill,</p>
<p>The &#8216;moaning&#8217; thing came across more harshly than I intended <img src='http://www.firstpartners.net/blog/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' />  </p>
<p>I don&#8217;t thing Struts 2 is *the* answer, I do think it is a big improvement. To use the bullet points from your original post:</p>
<p>* Verbosity: Better but not perfect. Fewer classes needed, more of them POJO and sensible defaults in the config file.</p>
<p>* Url pattern mapping: Slightly better, if this is a must have , then I&#8217;d recommend Spring MVC which is much more power in this area.</p>
<p>* Struts(-config).xml: Better , still suffering for the &#8216;one place to do config&#8217; &#8211; easy to know where to find stuff. Can use includes to split the file  if require.</p>
<p>* Not so difficult to test. Struts 2 is pretty much plain Java all the way &#8211; a lot easier to (J)unit test. My single biggest reason to make the move.</p>
<p>* Template support: Agree with you here. Use Sitemesh. Even better, use sitemesh pre configured with Struts2 (using Maven and Appfuse)</p>
<p>* MVC v the Web in general: I suppose it depends on the way that you think. Not matter what your point of view, At least Struts (2) isn&#8217;t as bad as JSF.</p>
<p>The underlying the bulk of my comment post: All these are reasons to move from Struts 1 (to framework of your choice). Convincing business users isn&#8217;t going to be as easy.</p>
<p>Paul</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bill de hOra</title>
		<link>http://www.firstpartners.net/blog/technology/2007/07/27/moaning-about-struts-1-wont-help-you-move-to-struts-2/comment-page-1/#comment-83920</link>
		<dc:creator>Bill de hOra</dc:creator>
		<pubDate>Fri, 27 Jul 2007 14:25:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.firstpartners.net/blog/technology/2007/07/27/moaning-about-struts-1-wont-help-you-move-to-struts-2/#comment-83920</guid>
		<description>&quot;Struts 2 is a huge improvement&quot;

Yes: 

http://www.dehora.net/journal/2006/02/web_frameworks_reloaded_just_use.html

&quot;Moaning about Struts 1 won&#039;t help you&quot;

Think of it as documentation. These problems are now written down in one place.  Given you think Struts 2 is the answer to Struts 1, I would think you&#039;d be happy to have something to link to that ratifies that.</description>
		<content:encoded><![CDATA[<p>&#8220;Struts 2 is a huge improvement&#8221;</p>
<p>Yes: </p>
<p><a href="http://www.dehora.net/journal/2006/02/web_frameworks_reloaded_just_use.html" onclick="javascript:pageTracker._trackPageview('/outbound/comment/www.dehora.net');" rel="nofollow">http://www.dehora.net/journal/2006/02/web_frameworks_reloaded_just_use.html</a></p>
<p>&#8220;Moaning about Struts 1 won&#8217;t help you&#8221;</p>
<p>Think of it as documentation. These problems are now written down in one place.  Given you think Struts 2 is the answer to Struts 1, I would think you&#8217;d be happy to have something to link to that ratifies that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: admin</title>
		<link>http://www.firstpartners.net/blog/technology/2007/07/27/moaning-about-struts-1-wont-help-you-move-to-struts-2/comment-page-1/#comment-83910</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Fri, 27 Jul 2007 13:27:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.firstpartners.net/blog/technology/2007/07/27/moaning-about-struts-1-wont-help-you-move-to-struts-2/#comment-83910</guid>
		<description>John,

That&#039;s pretty much what the Struts 1/ Struts 2 guys say as well :-)

Can&#039;t remember the URL, but they give a good , worked through, example on their site.

Paul</description>
		<content:encoded><![CDATA[<p>John,</p>
<p>That&#8217;s pretty much what the Struts 1/ Struts 2 guys say as well <img src='http://www.firstpartners.net/blog/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
<p>Can&#8217;t remember the URL, but they give a good , worked through, example on their site.</p>
<p>Paul</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John McClean</title>
		<link>http://www.firstpartners.net/blog/technology/2007/07/27/moaning-about-struts-1-wont-help-you-move-to-struts-2/comment-page-1/#comment-83908</link>
		<dc:creator>John McClean</dc:creator>
		<pubDate>Fri, 27 Jul 2007 13:17:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.firstpartners.net/blog/technology/2007/07/27/moaning-about-struts-1-wont-help-you-move-to-struts-2/#comment-83908</guid>
		<description>It should be possible to migrate in a piecemeal fashion. If the decision has been made that the current technology is sub-standard relative to the state-of-the-art it should be possible to mandate that new development be done with Struts 2, Spring MVC or whatever other technology (but please God, no JSF!) without rendering the legacy portion of the app obsolete (all that needs to happen is the front controller of the new framework respond to requests on a different uri pattern, and both can live side by side for a time). The influence of the old framework can be steadily reduced over time before being removed altogether from the mix...</description>
		<content:encoded><![CDATA[<p>It should be possible to migrate in a piecemeal fashion. If the decision has been made that the current technology is sub-standard relative to the state-of-the-art it should be possible to mandate that new development be done with Struts 2, Spring MVC or whatever other technology (but please God, no JSF!) without rendering the legacy portion of the app obsolete (all that needs to happen is the front controller of the new framework respond to requests on a different uri pattern, and both can live side by side for a time). The influence of the old framework can be steadily reduced over time before being removed altogether from the mix&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
