tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shapira, Yoav" <>
Subject RE: Private vs. protected?
Date Thu, 12 Jun 2003 12:41:55 GMT


>I've noticed many times that most, well, 'privates' in Tomcat (and many
>other Jakarta projects) are private, while having them protected would
>greatly ease coding any derivated classes, why?

There could be any number of reasons.  My guess is (and I know in my
code) many times stuff is left private when there's no immediate case in
mind why it should be protected.  

However, with tomcat, like other open-source projects, it's easy to
address this: you have the source code and can build it.  You can make
privates protected and add your subclass as you need it, then build your
own version of tomcat (or whatever the project is).  If you really thing
something should be protected, you can always suggest it as an
enhancement in bugzilla, along with your use case, and chances are in
the next product release it will indeed be protected.

Yoav Shapira

This e-mail, including any attachments, is a confidential business communication, and may
contain information that is confidential, proprietary and/or privileged.  This e-mail is intended
only for the individual(s) to whom it is addressed, and may not be saved, copied, printed,
disclosed or used by anyone else.  If you are not the(an) intended recipient, please immediately
delete this e-mail from your computer system and notify the sender.  Thank you.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message