| Summary: | Create JAXB Project, Create JAXB Classes from schema, Close project Receive NPE Error | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [WebTools] Dali JPA Tools | Reporter: | Jolene Moffitt <jolene.moffitt> | ||||
| Component: | JAXB | Assignee: | Paul Fullbright <paul.fullbright> | ||||
| Status: | VERIFIED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | cbridgha, karenfbutzke, neil.hauge | ||||
| Version: | 3.1 | Flags: | neil.hauge:
pmc_approved?
(david_williams) neil.hauge: pmc_approved? (raghunathan.srinivasan) neil.hauge: pmc_approved? (naci.dai) neil.hauge: pmc_approved? (deboer) neil.hauge: pmc_approved? (neil.hauge) neil.hauge: pmc_approved? (kaloyan) cbridgha: pmc_approved+ neil.hauge: review+ |
||||
| Target Milestone: | 3.2 RC1 | ||||||
| Hardware: | PC | ||||||
| OS: | Windows XP | ||||||
| Whiteboard: | PMC_approved | ||||||
| Attachments: |
|
||||||
|
Description
Jolene Moffitt
I get this even after reopening the workspace (i.e. there was no actual install operation in the current session.) I'm also able to get it without generating anything, just by having a single class. And it doesn't even have to have any annotations from the library. As far as I can tell, we aren't invoking any library provider API at all. Konstantin - any ideas what might be causing this? OK, what's happening is that, during validation, an library install delegate is constructed but not disposed. (It wasn't clear from docs that was required.) So I've added a dispose of that library install delegate. I also found a few other instances where a delegate was being constructed and not disposed (and found the same stack trace when closing the project) and I've addressed those as well. Created attachment 215014 [details]
patch
Patch looks good.
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 bug is caused by a leak of a library install delegate.
Is there a work-around? If so, why do you believe the work-around is insufficient?
No workaround to avoid the leak.
How has the fix been tested? Is there a test case attached to the bugzilla record? Has a JUnit Test been added?
Unit tests have been run.
Give a brief technical overview. Who has reviewed this fix?
This is boilerplate code that already exists in many other locations. See comment 2 for details. I have reviewed the fix.
What is the risk associated with this fix?
Very low risk.
looks good thanks committed for rc1 Verified in Build I-3.4.0-20120511050219 Verified a JAXB project can be opened and closed without error and with or without classes. See the link to view test steps for verification. http://wiki.eclipse.org/Dali_3.2_RC1 |