On Wed, 30 Apr 2014 06:43:53 -0300, Michael Wyraz
<michael.wy...@evermind.de> wrote:
Hi,
Hi!
for extending tapestrys internal service classes it's often required to
copy a lot of code because almost everything is private. Why not
changing it to protected to allow others to extend those classes?
Because it makes keeping backward-compatibility way harder and that's very
important for the project. Not to mention that protected fields are
something to be avoided in OOP. In addition, you can use advise or
overriding for dealing with most problems.
--
Thiago H. de Paula Figueiredo
Tapestry, Java and Hibernate consultant and developer
http://machina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org
For additional commands, e-mail: dev-h...@tapestry.apache.org
