| Summary: | NPE when removing/adding an adapter after CDO view closed | ||
|---|---|---|---|
| Product: | [Modeling] EMF | Reporter: | Esteban DUGUEPEROUX <esteban.dugueperoux> |
| Component: | cdo.core | Assignee: | Eike Stepper <stepper> |
| Status: | CLOSED FIXED | QA Contact: | Eike Stepper <stepper> |
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | 4.3 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 8 | ||
| Whiteboard: | |||
|
Description
Esteban DUGUEPEROUX
I have submited a fix and a update of the test as a review : https://git.eclipse.org/r/#/c/14444/ There is yet an issue, when executing the test of the review with EMF 2.8, the test failed on adapter removal, because with EMF 2.8 i.e. before the fix of https://bugs.eclipse.org/bugs/show_bug.cgi?id=325077, in MinimalEObjectImpl$ArrayDelegatingAdapterList.setData() there is a call to eInternalContainer(); which throws a LifecycleException. I see 2 possible fix, include the last release of MinimalEObjectImpl in the retrofix plugin or have the call to eInternalContainer(); does check if the CDOView is closed and return if it is closed instead of throwing a LifecycleException. What do you think about that? I've fixed this a little differently but it should fix the problem. In test cases please don't catch exception just to call fail("...") afterwards. That doesn't expose the exception in the JUnit view.
commit d4e32cc5f4c52db8c180441a147dd25690d036c3 Port to 4.2 via bug 414563. Closing. Closing. |