| Summary: | NPE in copySignatures method | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [WebTools] Java Server Faces | Reporter: | Xiaonan Jiang <xiaonan_jiang> | ||||
| Component: | JSF Tools | Assignee: | Carlin Rogers <carlin.rogers> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | david_williams, neil.hauge, raghunathan.srinivasan, robert_gallagher | ||||
| Version: | 3.0.3 | Keywords: | plan | ||||
| Target Milestone: | 3.2 RC1 | Flags: | raghunathan.srinivasan:
pmc_approved?
(david_williams) raghunathan.srinivasan: pmc_approved? (naci.dai) raghunathan.srinivasan: pmc_approved? (deboer) neil.hauge: pmc_approved+ raghunathan.srinivasan: pmc_approved? (kaloyan) raghunathan.srinivasan: review+ |
||||
| Hardware: | PC | ||||||
| OS: | Windows XP | ||||||
| Whiteboard: | PMC_approved Robustness | ||||||
| Attachments: |
|
||||||
|
Description
Xiaonan Jiang
See More info at the end of the description: More information: Maybe it's the side effect of https://bugs.eclipse.org/bugs/show_bug.cgi?id=269008. The variable "list" could be null in IJavaTypeDescriptor2Impl.copySignature() method. Created attachment 167767 [details] patch to check for null argument Attaching a patch that will check that the argument for the expected array of IType to copy in copySignatures() is not null. This does appear to be a downstream NPE due to the failure logged in Bug 269008. The failure in the call to TypeInfoCache.cacheSupertypesFor() gets logged in the underlying TypeInfoCache method, getOrCreateTypeInfo(), null is returned, and then passed into the copySignatures() of IJavaTypeDescriptor2Impl. This patch will protect against the additional NPE. This is a trivial fix and should be safe for 3.2RC1. Requesting consideration for PMC approval. * Explain why you believe this is a stop-ship defect. Or, if it is a "hotbug" (requested by an adopter) please document it as such. This is a fix for NPE that adopters have seen in the log file. * Is there a work-around? If so, why do you believe the work-around is insufficient? No workaround * How has the fix been tested? Is there a test case attached to the bugzilla record? Has a JUnit Test been added? Code review. There are no reproducible steps. * Give a brief technical overview. Who has reviewed this fix? See comment 2 * What is the risk associated with this fix? none-low Checked patch into HEAD for 3.2RC1 |