Bug 81063 - [model] Clarify the problem requestor paramter in becomeWorkingCopy
Summary: [model] Clarify the problem requestor paramter in becomeWorkingCopy
Status: VERIFIED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows XP
: P3 trivial (vote)
Target Milestone: 3.1 M5   Edit
Assignee: Jerome Lanneluc CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-12-15 04:32 EST by Dani Megert CLA
Modified: 2005-02-15 06:30 EST (History)
1 user (show)

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 Dani Megert CLA 2004-12-15 04:32:16 EST 
I20041214-2000

The API says:
@param problemRequestor a requestor which will get notified of problems detected
during reconciling as they are discovered. The requestor can be set to
code>null</code> indicating that the client is not interested in problems.


In the allowed use case of multiple clients e.g. client A calls the API with
problem requestor null, client B calls it with problem requestor B and client C
with problem requestor C. They could all expect that their problem requestor
gets notified which - I guess - isn't the case.
Comment 1 Jerome Lanneluc CLA 2005-01-05 07:02:14 EST 
Added the following sentences: 
 * Note that once in working copy mode, the given
 * {@link IProblemRequestor} is ignored. Only the original {@link 
 * IProblemRequestor} is used to report subsequent problems.
Comment 2 David Audel CLA 2005-02-15 06:30:36 EST 
Verified in I20050214-0927