| Summary: | NPE in SourceTypeBinding.resolveTypesFor | ||
|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | John Arthorne <john.arthorne> |
| Component: | Core | Assignee: | Satyam Kandula <satyam.kandula> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | amj87.iitr, byron, Olivier_Thomann, srikanth_sankaran |
| Version: | 3.3 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows Vista | ||
| Whiteboard: | stalebug | ||
|
Description
John Arthorne
I just noticed that it's using an internal class (Martin actually contributed this). Feel free to mark invalid if I'm doing something illegal here. This is another case when walking the binding hierarchy and trying to resolve more bindings that were not resolved before the scopes were flushed. Olivier - isn't this a case where the scopes shouldn't have been flushed already ? (i.e. not resetting the context) I guess yes. The scope should still be there for further resolution, but this is not the case. Satyam, this might be related to your actual investigation of improving binding handling. This still fails with my current implementation too. We should probably process the CU when we run into this mode. Need to find if we could safely do this. Do you have any other ideas? *** Bug 359478 has been marked as a duplicate of this bug. *** *** Bug 359478 has been marked as a duplicate of this bug. *** 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. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. 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. |