Jan,
sorry, I concentrated on your question, but missed the point that the behaviour was inconsistent between the class and the subclass.
I have currently no explanation.
I remember that in old releases of JDeveloper, we were always displaying the warning, even for Interfaces.We changed it - maybe too drastically (?)
I've made the following testing:
In the subclass, if I add someMethod(Number pSomeNumber):
public void someMethod(String pSomeString)
{
// still don't use pSomeString, but no warnings raised
}
public void someMethod(Number pSomeNumber)
{
// still don't use pSomeNumber; warnnig is raised
}
then I get the warning for this new one, overloading the super class method with a different parameter type.
So it does display the warning in the subclass when the signature is different.
Let me think of it. I'll come back to you later on this one.
Regards,
Didier.