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.
It would be easier to have a method to check whether Element (from JavaHierarchyAPI) is writeable or not. E.g.: classElement.isReadOnly() instead of getting its DataObject then its primary file and calling its isReadOnly method.
FWIW I could use this for the Class Navigator as well, to determine if a class is overridable or not. Piotr, please keep in touch on what you do with parsing method bodies - I've got some strange ideas for alternate views of method bodies (see LinesLook in the the class navigator - crude and nearly useless now, but for editing huge procedural-code style methods, something that shows you what bracket nesting level you're in might be useful) - I'd like to implement something like "Split into method" so you can select a block of code and move it to its own method. To do that, I'll need to figure out what members are accessed, and their types.
We should add such method to the JMI API.
Javacore module was replaced by Retouche infrastructure. This bug is not valid in trunk any more.
Reorganization of java component