While a progID for the component manager has been defined (<http://lxr.mozilla.org/seamonkey/source/xpcom/components/nsComponentManagerUtils.h#61>), it doesn't look like this ever gets registered. Thus attempts to get this service via its progID fail.
*** Bug 44979 has been marked as a duplicate of this bug. ***
I am trying to figure out which XPCOM methods need to be exported. I assume that this should be the only method exported from XPCOM to get the component manager, right? If so, I nominate this for nsbeta3. If not, then it doesn't seem very important.
Would whoever marked this nsbeta3+ please supply a simple use case why this particular progid needs to be registered in component manager?
Could you please explain why you want to get the component manager via its progid? I can think of a reason or two you might want to do this, but it seems that the component manager is readily available without being registered. Might the real solution not be just delete the definition? It is also not clear that this is a nsbeta3 bug.
Edward: Welcome to xpcom!
Once again... attempting to reassign from Ray to Edward.
Since rayw's comments on 2000-08-31, there was no response as to why this is needed. I agree, and am therefore closing this bug.
Edward, rayw did not suggest that this bug was invalid. Rather, he suggested that a possible solution would be deleting the definition of the contractID.
To be clear, I don't see any problem with rayw's recommendation. But it is silly to have a contractID defined that never gets registered.
reassign all kandrot xpcom bug.
I am marking this as wont fix. Currently, if you have the service manager, you should be able to qi it to the component manager.
WONTFIX doesn't make sense here. If the verdict is, as you say, that the contractID should not exist, then the fix is simply to eliminate it. Keeping the contractID around when it's never registered is just confusing.
This has been removed.