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

Bug 362847

Summary:	ServiceRegistry getService should return immediately
Product:	[ECD] Orion	Reporter:	Simon Kaegi <simon_kaegi>
Component:	Client	Assignee:	Simon Kaegi <simon_kaegi>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	john.arthorne, susan
Version:	0.3
Target Milestone:	0.4 M1
Hardware:	PC
OS:	Windows 7
Whiteboard:

Description Simon Kaegi

2011-11-03 18:06:48 EDT

Currently ServiceRegistry.getService(...) returns a promise instead of the service or null as with OSGi. At the time I thought this was clever because it meant we effectively had a ServiceTracker built right in. With experience I can see now that OSGi got the abstraction right and it's not helpful and actually causes us to take advantage of an implementation detail of dojo.Deferred when we want the service immediately.

ServiceRegistry.getService(...) should either return the Service or null immediately just like how it does with OSGi.

Comment 1 John Arthorne

2011-11-04 08:36:27 EDT

I thought we took advantage of this asynchronous behaviour to avoid being sensitive to script load ordering differences. I guess we'll find out when you try changing it...

Comment 2 John Arthorne

2011-11-04 12:04:19 EDT

If you're looking for the code you wrote for this bug, ping Susan ;)

Comment 3 Simon Kaegi

2011-11-10 16:50:55 EST

Fixed in b2ca594c1adbf7494819a8ea545f6b50dd737879