This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 36327 - Registry: cannot follow threading model to achieve proper synchronization in MergedContexts
Summary: Registry: cannot follow threading model to achieve proper synchronization in...
Status: RESOLVED WONTFIX
Alias: None
Product: contrib
Classification: Unclassified
Component: Registry (show other bugs)
Version: 3.x
Hardware: PC All
: P3 blocker (vote)
Assignee: Jiri Skrivanek
URL:
Keywords: API
Depends on:
Blocks:
 
Reported: 2003-09-29 11:16 UTC by rmatous
Modified: 2008-12-22 13:54 UTC (History)
1 user (show)

See Also:
Issue Type: TASK
Exception Reporter:

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 rmatous 2003-09-29 11:16:32 UTC 
SPI documentation says: "SPI clients do not have
to synchronize anything". But I must synchronize
acces to all delegates and simultanously to its 
MergedContext. Could be convenient to have one
shared Mutex for all Contexts.
Comment 1 rmatous 2003-09-29 11:17:15 UTC 
Probably requires API change.
Comment 2 David Konecny 2003-09-29 11:44:09 UTC 
Yes, it's been decided to simplify threading model of Registry even
more and have only one global Registry Mutex.
Comment 3 David Konecny 2004-11-01 14:45:13 UTC 
This was partially fixed by Radek and there is already one mutex for
all operations. But there are still things to be fixed. For example
context listeners are added directly to SPI context what means that
SPI implementor must take case about firing events under mutex read
lock. Could this be done directly by the API context? If not it should
be at least documented in SPI docs.
Comment 4 Antonin Nebuzelsky 2008-04-15 17:02:38 UTC 
Reassigning to new module owner jskrivanek.
Comment 5 David Konecny 2008-04-15 22:17:30 UTC 
Registry module is obsolete.