This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
When I use this method in my module, sometimes this method returns null when the super class is java.lang.Object and sometimes it returns java.lang.Object. It seems that when the original class is in a .jar file and only the .class is available it returns java.lang.Object as the superclass. This is causing my windows to display information about a class's methods inconsistently because sometimes Object's methods appear and other times they don't.
Sorry, this is (currently) as designed: superClass property reports what is explicitly written in either class file or java file. If you had a .java file with public class Foo extends Object { } its ClassElement.getSuperclass() would return j.l.Object as well. In .class files, the reference is always explicit. My colleagues are designing a better model for source manipulation, so I changed the issue to an enhancement request for them
Fixed in 4.0.