This content has been marked as final. Show 4 replies
I don't think there is anything wrong with it here. ADF BC has its rules in which it creates setter/getter methods. In the class the method is created, the method name and arguments must be unique to not cause a conflict. So IMO it all comes down to naming conventions to prevent this type of overrides.
I agree that naming conventions can avoid this type of issue. Nevertheless, as a matter of usability and reliability, I think it would be good if JDeveloper at least gives a warning during code generation when it generates methods which would override a method from a superclass.
In any case, I have logged a bug, lets see how it evolves...