| Summary: | [DS] ClassCircularityError when activating services | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] Equinox | Reporter: | Bryan Hunt <bhunt> | ||||
| Component: | Compendium | Assignee: | Stoyan Boshev <s.boshev> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | edward.costello, s.boshev, tjwatson | ||||
| Version: | 3.7 | ||||||
| Target Milestone: | Juno M4 | ||||||
| Hardware: | PC | ||||||
| OS: | Mac OS X - Carbon (unsup.) | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Bryan Hunt
I would have thought the fix in bug316780 would have prevented this. (In reply to comment #1) > I would have thought the fix in bug316780 would have prevented this. It seems the fix in bug316780 fixes only partially the ClassCircularityError problems. According to the given exception stack trace, now the ClassCircularityError occurs within the implementation of the refection classes (NativeMethodAccessorImpl) therefore it is processed there and a new exception java.lang.reflect.InvocationTargetException is thrown containing the cause. In this case the SCR code does not handle the ClassCircularityError. I will modify the SCR code to process also this situation. *** Bug 327413 has been marked as a duplicate of this bug. *** Created attachment 207328 [details] proposed patch This patch does not solve the ClassCircularityError issue. It just makes sure the affected component will be processed asynchronously by SCR thus avoiding the detected ClassCircularityError. This completes the efforts done for resolving bug316780 Patch released in master |