Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 333467 - [ReferenceDescriptions] Find a better compromise between consistency and lazy initialization
Summary: [ReferenceDescriptions] Find a better compromise between consistency and lazy...
Status: CLOSED FIXED
Alias: None
Product: TMF
Classification: Modeling
Component: Xtext (show other bugs)
Version: 2.0.0   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: M5   Edit
Assignee: Jan Koehnlein CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-01-04 08:13 EST by Jan Koehnlein CLA
Modified: 2017-09-19 18:07 EDT (History)
1 user (show)

See Also:
jan: indigo+


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jan Koehnlein CLA 2011-01-04 08:13:35 EST
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.
Comment 1 Jan Koehnlein CLA 2011-01-04 08:15:59 EST
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.
Comment 2 Jan Koehnlein CLA 2011-01-04 10:25:30 EST
Pushed to MASTER
Comment 3 Karsten Thoms CLA 2017-09-19 17:56:19 EDT
Closing all bugs that were set to RESOLVED before Neon.0
Comment 4 Karsten Thoms CLA 2017-09-19 18:07:09 EDT
Closing all bugs that were set to RESOLVED before Neon.0