| Summary: | RWOLockManager.unlock(CONTEXT) gives ConcurrentModEx | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Modeling] EMF | Reporter: | Caspar D. <caspar_d> | ||||||||
| Component: | cdo.core | Assignee: | Caspar D. <caspar_d> | ||||||||
| Status: | CLOSED FIXED | QA Contact: | Eike Stepper <stepper> | ||||||||
| Severity: | normal | ||||||||||
| Priority: | P3 | CC: | saulius.tvarijonas | ||||||||
| Version: | 4.1 | Flags: | stepper:
review+
|
||||||||
| Target Milestone: | --- | ||||||||||
| Hardware: | All | ||||||||||
| OS: | All | ||||||||||
| Whiteboard: | |||||||||||
| Attachments: |
|
||||||||||
|
Description
Caspar D.
Created attachment 200519 [details]
Patch v1
Created attachment 200521 [details]
Patch v2
v2 of the patch renames the maps and a method involved with updating
the contextToLockStates map.
I know you (Eike) renamed the method before, but I really believe the
name 'removeLockFromContext' is deceiving. First, what's being removed
is a LockState object, which is a combination of locks, not a single
lock. And second, it's not being removed from a context; rather, it's
being removed from the set of all lockStates that a given context is
involved in. I added JavaDocs to the method, to this effect.
(Functionally patch v2 is the same as v1.)
PS. I recommend looking at patch v1 first, because it shows how minimal the fix is. Created attachment 200524 [details]
Patch v3 (left-over tests removed)
Committed revision 8839. Closing. |