Bug 33530 - JavaModel synchronization model should be more optimistic
Summary: JavaModel synchronization model should be more optimistic
Status: VERIFIED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 2.1   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: 3.0 M2   Edit
Assignee: Jerome Lanneluc CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-02-28 07:21 EST by Philipe Mulet CLA
Modified: 2003-07-16 08:10 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Philipe Mulet CLA 2003-02-28 07:21:12 EST 
Build 2.1RC1

JavaElement#getElementInfo is locking for the entire duration of the info 
computation, even if info is available in cache already.

The current reason is that some elements are populated in a way leading some 
infos to be placed in the cache in an non-initialized state (see 
CompilationUnit#generateInfos).

The JavaModel should be more optimistic, and only store infos when they are 
complete. The locking should only occur when updating the cache.
Comment 1 Philipe Mulet CLA 2003-02-28 10:03:25 EST 
Defer
Comment 2 Philipe Mulet CLA 2003-04-02 06:42:34 EST 
reopen
Comment 3 Jerome Lanneluc CLA 2003-06-10 06:27:10 EDT 
Element infos are now created outside the JavaModelManager lock in a temporary 
cache. The are copied atomically in the JavaModelCache.
Comment 4 David Audel CLA 2003-07-16 08:10:13 EDT 
Verified.