| Summary: | CCE in metadata framework with TestableProjectFactoryStrategy.perform() casting a workspace to a project | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [WebTools] Java Server Faces | Reporter: | Carlin Rogers <carlin.rogers> | ||||
| Component: | Core | Assignee: | Gerry Kessler <gerry.kessler> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | cameron.bateman, david_williams, gerry.kessler, raghunathan.srinivasan | ||||
| Version: | 3.2 | Flags: | david_williams:
pmc_approved+
raghunathan.srinivasan: pmc_approved? (naci.dai) deboer: pmc_approved+ raghunathan.srinivasan: pmc_approved? (neil.hauge) raghunathan.srinivasan: pmc_approved? (kaloyan) raghunathan.srinivasan: review+ cameron.bateman: review+ |
||||
| Target Milestone: | 3.2 RC3 | ||||||
| Hardware: | PC | ||||||
| OS: | Windows XP | ||||||
| Whiteboard: | PMC_approved | ||||||
| Attachments: |
|
||||||
|
Description
Carlin Rogers
Created attachment 169904 [details]
Fix
This exception will only occur if the project is null in a metadata context which is something that is not typical, but is allowed currently but deprecated by the framework. The JUnit test that throws the exception uses a null project. Since a null project context may be being used by adopters, it is more than just a fix for a JUnit. I therefore have marked this as a candidate for RC3. * 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 stop-ship defect. Adopter products could be using the metadata framework similar to that in the Junit test resulting in a CCE. * Is there a work-around? If so, why do you believe the work-around is insufficient? No reasonable workaround * How has the fix been tested? Is there a test case attached to the bugzilla record? Has a JUnit Test been added? Verified by running the affected junit test. * Give a brief technical overview. Who has reviewed this fix? See comment 2 * What is the risk associated with this fix? low I'm fine with this, but I do always get nervous seeing inheritance change this late in the game, so please double check if that's the best solution. Is there any chance this could impact adopters? I know its "internal" ... but, is it the sort of thing anyone would be tempted to (incorrectly) use in a "instanceof" statement? Any reason TestableResourceFactoryStrategy should maybe extend the original TestableProjectFactoryStrategy instead of just implement ISimpleStrategy? I'm asking all this in the spirit of getting you to look twice :) I've no knowledge of this code, and just took a quick glance at patch. But, it is only a 'normal' bug. So .. if there's any risk with current solution, please have others review if inheritance solution is best. But, again, I'm fine with what ever you decide. Additional review by Cam. Checked into HEAD 5/26/10. |