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

Bug 348265

Summary: [client] Content assist should not know about serviceregistry
Product: [ECD] Orion Reporter: Mark Macdonald <mamacdon>
Component: EditorAssignee: Mark Macdonald <mamacdon>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: P3    
Version: 0.2   
Target Milestone: 0.3 M2   
Hardware: PC   
OS: Windows 7   
Whiteboard:

Description Mark Macdonald CLA 2011-06-03 15:14:25 EDT 
At the moment ContentAssist will accept an optional serviceregistry parameter. If this is provided, it is used to obtain the content assist proposals based on the file type. If the parameter is omitted, you can add proposal providers directly through API (as in the embeddededitor example).

Knowledge of the registry should be removed from ContentAssist. In the Orion case (where we do need to consult the serviceregistry to find the content assist providers) that should be done by the glue code.