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.
Summary: | Provide a fast-and-dirty parser for class/interface inheritance hierarchy | ||
---|---|---|---|
Product: | java | Reporter: | Petr Jiricka <pjiricka> |
Component: | Unsupported | Assignee: | issues@java <issues> |
Status: | RESOLVED FIXED | ||
Severity: | blocker | Keywords: | PERFORMANCE |
Priority: | P2 | ||
Version: | 3.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | ENHANCEMENT | Exception Reporter: |
Description
Petr Jiricka
2002-10-17 09:00:27 UTC
That can be IMHO done for top-level classes, but there may be inner classes as well. They are quite peculiar, because for top-level classes, only imports and the package statement determine scope for identifier resolution. Inner classes may use types inherited from the outer class' superclasses. So - quick & dirty: might be, but *only* for top-level classes and really fast only if only first class in the file is scanned. I think it is sufficient to only do this for the first top level class and no inner classes, especially for the purpose of recognition by DataLoaders. The only problem could be if there are multiple top-level classes, and the first one is not the public one, but I would say this is a corner case which does not need to be considered. A question: will it be possible to implement this feature for NB 4.0? This release will cache the inheritance information in a persistent storage, so information from this storage could potentially be used by the dataloader which would like to recognize all servlets, correct? Thanks. Yes, that's correct. Fixed by new JMI based java model Reorganization of java component |