是否可以隐藏或降低对Java中的“继承方法”的访问？

// Defines myMethod
public class Base {
    protected void myMethod() {}
}

// Uses myMethod and then hides it.
public class DerivedOne extends Base {
    @Override
    private void myMethod();
}

// can't access myMethod.
public class DerivedTwo extends DerivedOne {

}

我认为你提出的问题的性质暴露了你的对象模型的概念问题.在实际上你应该做的是描述“有一个”或“使用”关系时,你正在努力将各种各样的责任描述为“是一种”关系.您希望从一个子类隐藏基类功能的事实告诉我,这个问题实际上并不映射到三层继承树上.

听起来你正在描述一个经典的ORM问题.让我们再来看看,看看我们是否可以将其重新映射到其他概念上,而不是严格的“是”继承,因为我真的认为你的问题不是技术性的,它是概念性的：

你说：

The base class is the base table class
managing the database handling part of
it. There is a fair amount of
functionality contained in it that is
common to all table types – as once
they are in the database they become
uniform.

这可能更清楚,但是听起来我们有一个类需要管理数据库连接和通用数据库操作.在Single Responsibility之后,我想我们在这里完成.您不需要扩展此类,您需要将其交给需要使用其功能的类.

The middle class is specific to the
kind of table in the file being
parsed,and has the table parsing and
import logic. It needs access to some
of the base class’s database access
functions.

这里的“中产阶级”听起来有点像Data Mapper.这个类不需要扩展上一个类,它需要拥有它的引用,也许注入到构造函数或一个设置器作为接口.

The top level class is specific to the
table and does nothing more than
initialize the table’s layout in a way
the parent classes can understand.
Also users of the base class do not
need to see or access the database
specific functions which the middle
class do. In essence,I want to reveal
these functions only to one level
above the base class and no one else.

我不清楚为什么一个高级别的类似乎有数据库模式的知识(至少这是短语“初始化表的布局”对我来说),但是再一次,如果前两个类之间的关系是encapsulation (“has a”/”uses a”) instead of inheritance (“is a”)我不认为这是一个问题.