At 5:18 PM -0400 6/12/06, Ted Husted wrote:
In the field, it seems like that once a Struts application hits
production, it continues to use the same version. A new application
might use 1.2, but the old ones continue to plug along on 1.1. If it
ain't broke, why fix it?
This is definitely not true in my shop. We usually find it very
constraining when going back to an older app and adding new features
if we can't bring the app up to "modern practices."
Our environment may be somewhat unusual, in that our sales people
often sell small enhancements to existing projects, and they often
sell "the same thing" we just implemented in a new app to a client
whose project is 3 years and two versions of Struts old.
Also, we find it pretty cumbersome to mentally switch between what
can and can't be done between different versions of apps (this isn't
only Struts changes, but also catching up with servlet, JSP, and JSTL
evolution.)
Joe
--
Joe Germuska
[EMAIL PROTECTED] * http://blog.germuska.com
"You really can't burn anything out by trying something new, and
even if you can burn it out, it can be fixed. Try something new."
-- Robert Moog
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
