On 12/4/2000 at 4:49 PM [EMAIL PROTECTED] wrote:
> As Jean-Baptiste said, surely the right way to do it is to add or
extend classes?
Developers in the open source community have always patched code to
meet specific requirements. A prime argument for open source is the
ability to choose between patching and extending. Obviously, developers
who patch take the responsbility for applying the patch again later.
And, of course, Thor could have posted questions about his patch to the
list first. But now that the article is published <
http://www.javaworld.com/javaworld/jw-12-2000/jw-1201-struts.html >,
lets ask the questions:
"How could Struts accomplish the same result without a patch?"
and/or
"Should these patches be added to Struts?"
If alternates turn up, they could be posted somewhere as an addendum to
the article. (Or, in a followup article?) It might also be nice to see
another addendum that addressed the shortcomings Craig mentioned <
http://www.mail-archive.com/struts-user%40jakarta.apache.org/msg00891.ht
ml >.
But, let's see some code, guys.
Personally, I think Thor's interfaces seem useful, and I may add his
patches to my own code base.
-- Ted Husted, Husted dot Com, Fairport NY USA.
-- Custom Software ~ Technical Services.
-- Tel 716 425-0252; Fax 716 223-2506.
-- http://www.husted.com/
