Hi Oleg
Thanks for sharing your thoughts on this. How do you support the point you
are making? Why should source code not be changed? What is the harm, within
a specific project, to change the source code to add functionality? How
would an open source project ever evolve if all experiments where banished?
Should there be a monopopy on making suggestions?
Regards
Thor
-----Original Message-----
From: Oleg V Alexeev [mailto:[EMAIL PROTECTED]]
Sent: Montag, 4. Dezember 2000 19:41
To: Thor Kristmundsson
Subject: Re[2]: Article on JavaWorld
Hello Thor,
It is wrong solution, for my mind, to rewrite source instead of extend
struts classes to incorporate your own functionality. Of course, you
CAN do it, but it is wrong. I speak about tags not about BeanUtils
class - all tag classes can extended to implement additional
functionality (thanks to Craig - final keyword removed.. 8))) )
Monday, December 04, 2000, 6:01:32 PM, you wrote:
TK> You have a point, the article doens't make use of all of Struts feature.
I
TK> was simply trying to convey the experience I got during a recent project
of
TK> using the Struts JSP tag libraries. This project didn't lend itself to
using
TK> the rest of Struts so I had nothing to report there. IMHO the methods
TK> presented do add value to Struts and could perhaps be incorporated. I
cant
TK> see anything inherently wrong with changing the Struts code to
accomodate
TK> these features.
TK> Thor Kristmundsson
--
Best regards,
Oleg mailto:[EMAIL PROTECTED]
