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

Bug 317441

Summary: [JFace] JFace plugin should be a singleton
Product: [Eclipse Project] Platform Reporter: Krzysztof Daniel <krzysztof.daniel>
Component: UIAssignee: Platform UI Triaged <platform-ui-triaged>
Status: CLOSED DUPLICATE QA Contact:
Severity: normal    
Priority: P3 CC: bokowski, daniel_megert, prakash, pwebster, remy.suen, tjbishop
Version: 3.4.2   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard:

Description Krzysztof Daniel CLA 2010-06-21 09:35:15 EDT 
It uses SWT, offers some registries. It is also UI plugin, and all other UI plugins are singletons.
Comment 1 Troy Bishop CLA 2010-06-21 09:59:58 EDT 
The same may apply for the org.eclipse.jface.text and org.eclipse.jface.databinding bundles.
Comment 2 Remy Suen CLA 2010-06-21 10:00:47 EDT 
(In reply to comment #1)
> The same may apply for the org.eclipse.jface.text and
> org.eclipse.jface.databinding bundles.

Please open a separate bug against Platform/Text for the org.eclipse.jface.text case.
Comment 3 Paul Webster CLA 2010-06-21 10:08:11 EDT 
What determines if it must be a singleton is if you cannot have 2 versions of the bundle running at the same time.

ex: anything that provides extension/extension points must be a singleton.

SWT is a special case because of the singleton nature of the Display and the native libs (similar to com.ibm.icu, which uses no extensions but mimics the singleton Locale/Calendar APIs).

Is there something to prevent jface 3.5.x and jface 3.6 running on a 3.6 SWT?

PW
Comment 4 Boris Bokowski CLA 2010-06-21 12:11:12 EDT 
(In reply to comment #3)
> Is there something to prevent jface 3.5.x and jface 3.6 running on a 3.6 SWT?

Sounds like a fun experiment to try ;-)
Comment 5 Dani Megert CLA 2014-12-08 08:06:16 EST 

*** This bug has been marked as a duplicate of bug 388359 ***