Community
Participate
Working Groups
Currently, the exported EObjects and the reference descriptions of a DefaultResourceDescriptions are computed independently on demand. If a resource changes between the calls to getExportedEObjects() and getResourceDescriptions(), the user will get inconsistent results without any notice. In general, we manage concurrent access externally, e.g. with document IUnitOfWorks (dirty state) or workspace resource locks (persistent builder state). We should ensure that clients get consistent EObjectDescriptions and ReferenceDescriptions if they stick to these synchronization practices.
Internal discussion yielded, that we rather store IEObjectDescriptions and IReferenceDescriptions in the resource cache than in the DefaultResourceDescription itself, such that they get evicted automatically on resource changes.
Pushed to MASTER
Closing all bugs that were set to RESOLVED before Neon.0