Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 333467

Summary:	[ReferenceDescriptions] Find a better compromise between consistency and lazy initialization
Product:	[Modeling] TMF	Reporter:	Jan Koehnlein <jan>
Component:	Xtext	Assignee:	Jan Koehnlein <jan>
Status:	CLOSED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	tmf.xtext-inbox
Version:	2.0.0	Flags:	jan: indigo+
Target Milestone:	M5
Hardware:	All
OS:	All
Whiteboard:

Description Jan Koehnlein

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

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

2011-01-04 10:25:30 EST

Pushed to MASTER

Comment 3 Karsten Thoms

2017-09-19 17:56:19 EDT

Closing all bugs that were set to RESOLVED before Neon.0

Comment 4 Karsten Thoms

2017-09-19 18:07:09 EDT

Closing all bugs that were set to RESOLVED before Neon.0