UnregisterComponent shouldn't return nsresult. It should never fail, causing the NSUnregisterSelf to bail and not finish unregistering stuff.

You might want to make this change at the same time you split out NSRegisterSelf and NSUnregisterSelf into an interface. While you're at it, you should clean up everything to use GenericFactory -- actually a subclass of GenericFactory that requires callbacks for RegisterSelf and UnregisterSelf (along with the DLL version number, name, etc.)

Moving all current open XPCOM and XPCOM Registry bugs to rayw since dp is on sabbatical. rayw is now default assignee for these components.

This is part of a large number of issues related to "Registering Components in XPCOM". The interface that already contains registration and unregistration is nsIModule, and does not return anything. The problem is that lots of DLLs are not using it as they should.

Assigning rest of xpcom stuff to myself (from Ray).

dp is no longer @netscape.com. changing qa contact to default for this product

reasigning warren bugs to default component owners.

reassign all kandrot xpcom bug.

conrad, is unregistration implied w/ "replace" in the component manager?

I disagree. everything can fail. I think that interface methods should return nsresult's and code should deal with it. marking invalid. reopen if opinions differ.

Marking wont fix.