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: | Editor API uses too much reflection | ||
---|---|---|---|
Product: | editor | Reporter: | emi <emi> |
Component: | -- Other -- | Assignee: | Milutin Kristofic <mkristofic> |
Status: | RESOLVED WONTFIX | ||
Severity: | blocker | Keywords: | API |
Priority: | P4 | ||
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | ENHANCEMENT | Exception Reporter: |
Description
emi
2007-08-21 12:10:53 UTC
Could you please identify the offending places? Also, are you really referring to 5.0 source base? If so, I would suggest to look at the trunk sources. It's not that they would be better, but I don't see much point in analyzing sources that are two releases old. Anyway, thanks for the effort, really. No, my mistake, it's the 6.0 sources. Basically just go in editor and do a grep on Lookup.getDefault().lookup(ClassLoader.class) for example. That's something we shouldn't have at all. Also lots of usage of java.lang.reflect.Field/Method. I find it disturbing that after all these ways to define services, etc. I still see reflection. Ok, I'll go through the sources and try to compile the list. I expect some of the occurrences could be there for preserving backwards compatibility of old/deprecated stuff. But as you said, reflection should not be used in normal code. moving opened issues from TM <= 6.1 to TM=Dev This old bug may not be relevant anymore. If you can still reproduce it in 8.2 development builds please reopen this issue. Thanks for your cooperation, NetBeans IDE 8.2 Release Boss |