At 9:17 PM -0700 10/13/05, Paul Benedict wrote:
Does anyone ever run any custom versions of Struts or
the Commons library? The reason I ask is because the
bug that I need fix (it is now fixed) in Commons
Validator isn't released for the Struts 1.2.x branch,
but most likely will be released with Struts 1.3....
Well I don't like using release 1 of anything :-) I
wouldn't want to upgrade to Struts 1.3 until it at
least gets into version 1.3.3 or something - the
theoretical risk for large bugs is high... Just think
of how many releases were for Struts 1.2!
Yes, but think of how many applications are in production right now
built on Struts 1.1, or on Struts 1.2.[x<7]. Most of the changes
from version to version of Struts are feature enhancements, and most
of the bug fixes clearly don't prevent most people from building
applications that operate perfectly well even while the identified
bug has not been fixed.
My team and I have put three Struts 1.3.x webapps into production so
far, and we're working on more all the time. I'm certain it's
possible that there are bugs in there that just haven't been
exercised given some particulars of how we write webapps, but it's
not like it was rewritten from the ground up.
So what's the right solution here? I would like to see
a Strut 1.2.8, as I said, with an upgraded Commons
Validator too. Do I just compile a custom version of
Validator for myself? I'd like to hear opinions.
If this particular bug is in commons-validator, then why do you need
a different version of Struts? Sorry, I haven't been following the
validator development extremely closely, but if the bug isn't in
Struts, why is the release version of Struts a concern?
Struts, as with most open source code, doesn't go through the kind of
testing process prior to a versioned release that you might imagine
if you are thinking of commercial software.
I don't know if that clarifies anything or not.
Joe
--
Joe Germuska
[EMAIL PROTECTED]
http://blog.germuska.com
"Narrow minds are weapons made for mass destruction" -The Ex
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
