Bug 37838 - Clarify IWorkspace.validateEdit spec for UI context use
Summary: Clarify IWorkspace.validateEdit spec for UI context use
Status: RESOLVED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Resources (show other bugs)
Version: 2.1   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: 3.0 M5   Edit
Assignee: Platform-Resources-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-05-19 12:16 EDT by Knut Radloff CLA
Modified: 2003-10-22 17:37 EDT (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 Knut Radloff CLA 2003-05-19 12:16:57 EDT 
build 20030516

It is not clear whether IWorkspace.validateEdit has to be called from the UI 
thread when a UI context is passed in or if the VCM provider has to do the 
required switch. I believe the responsibility to switch to the UI thread when 
the UI context is actually used should rest with the implementor of 
IFileModificationValidator. 
This was brought up in bug 37189.
IWorkspace/IFileModificationValidator specs should be clarified.
Comment 1 Sandeep Grewal CLA 2003-08-23 10:10:14 EDT 
Hi,
Wanted to know the current status and opinion of development regarding the 
issue. Is this a design issue?
Thanks in advance.
Sandeep
Comment 2 John Arthorne CLA 2003-10-22 17:37:46 EDT 
As with all resources plugin API, validateEdit can be called from any thread. 
It is the responsibility of the IFileModificationValidator implementation to
interact with the UI context in an appropriate thread.  I have added this
clarification to the spec.