Bug 61040 - Should add protect for reentrance to #getResolvedClasspath
Summary: Should add protect for reentrance to #getResolvedClasspath
Status: VERIFIED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.0 M9   Edit
Assignee: Jerome Lanneluc CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-05-05 09:25 EDT by Philipe Mulet CLA
Modified: 2004-05-18 13:47 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 2004-05-05 09:25:29 EDT 
Build 20040428

This is the counterpart of bug 60437 in JDTCore.
We should be internally setting the resolved classpath to an empty path, while 
computing the resolvedClasspath itself, since we are going to call out to 
client code when requesting container entries.

If client is misbehaving, then infinite recursion will occur.
Comment 1 Jerome Lanneluc CLA 2004-05-07 07:23:41 EDT 
Changed getResolvedClasspath() to return an empty classpath if a clients asks 
for the resolved classpath while it is being resolved.

Added regression test ClasspathInitializerTests.testContainerInitializer9()
Comment 2 Frederic Fusier CLA 2004-05-18 13:47:03 EDT 
Verified for 3.0 M9 with build I200405180816.