Community
Participate
Working Groups
I talked with Frederic Fusier and provided him with the Jar test case. Code example: new SearchEngine().searchAllTypeNames( null, null, scope, requestor, waitingPolicy, monitor); Actual Result: I got some anonymous class types. Expected Result: SearchEngine.searchAllTypeNames is supposed to filter out all anonymous class types.
I got the jar file from Ahmed which helps me to reproduce the problem. This issue can be workarounded by client by filtering received match with empty element name: TypeNameMatchRequestor requestor = new TypeNameMatchRequestor() { public void acceptTypeNameMatch(TypeNameMatch match) { IType type = match.getType(); if (type.getElementName().length() == 0) { System.out.println("filter anonymous class!"); } } }; Ahmed, as the workaround is really simple, would you accept to decrease the severity of this bug to 'normal' instead of 'major'?
sure
The problem comes from the class file stored in the jar file. E.g. IBMKeyManagementServer.jar\com\ibm\keymanager\keystore\KeyStoreLoader$1 does not have any innerInfo set, hence is not recognized as an anonymous by our ClassFileLoader... Was the jar file build with any obfuscator which could explain the missing inner information?
Please provide requested information, thx
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
