b3b9a205df
r=dougt ComponentManager talks to factories when it's asked to create components or get services. The factories are expected to return success when they provide an object or return a failure code and provide a null pointer. Unfortunately, it's trivially easy for someone writing a js xpcom component to mess up their factory such that they return success without providing an object. In this case we will now throw NS_ERROR_SERVICE_NOT_FOUND. I've picked this because we did not find a factory capable of properly servicing our request :) -- and because there's no better result available :(. This branch eventually deserves PR_LOGGING so that people could see it even if they didn't build debug (but did somehow get prlogging), but that's left for a future patch. git-svn-id: svn://10.0.0.236/trunk@203727 18797224-902f-48f8-a5cc-f745e15eee43