IMHO, major framework upgrades for existing application, in general is unworthy of the cost, headache, and the gotchas that they never tell you about. If there are new compelling business-value-producing features in the upgrade, more than likely you have to redesign the application. That's another story and can take a business project life of its own.
If you starting a new application development, though, it's better always to do it in the new framework and roll the above mentioned cost into the project cost. Off course framework vendors or authors don't see it that way :) Regards, --------------------------------------- Medhat M. Saleh agillaire, Inc. [EMAIL PROTECTED] Office: (972) 966-3528 -----Original Message----- From: Zsolt Koppany [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 10, 2007 9:55 AM To: Struts Users Mailing List Subject: Moving from struts-1 to struts-2 or spring mvc Hi, we have a pretty large code in struts-1. What is more complicated moving to struts2 or spring mvc? Zsolt --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
