[Project_owners] fixing xml-rpc

Matthew Wilson matthew at mjwilson.demon.co.uk
Tue Apr 12 09:42:58 EDT 2005

Ilya Pogorelsky wrote:
> I have been trying to use xml-rpc client built into mozilla.
> Doing fairly simple xml-rpc, I kept running into the following exception:
> Error! <(80470002) Component returned failure code: 0x80470002 
> (NS_BASE_STREAM_CLOSED) [nsIScriptableInputStream.available]>
> I went ahead and dug a little bit into the XPCOM javascript code which 
> implemented the xmlrpc client.
> On first pass it appeared that there was some bug in xml parsing code.
> I did a little searching on the NET and found instructions on mozblog 
> install site telling met that I should replace nsXmlRpcClient.js (ie 
> xpcom implementation of xmlrpc client) with what appears to be an older 
> version of the xmlrpc client. The older client appears to have resolved 
> the parsing problems.
> On the one hand I am happy to have found a resolution, but, on other 
> hand I am a bit concerned about the fact that the shipped version of the 
> xpcom client is broken. Since I am embarking on a sizable project which 
> utilizes XUL for the front end, I am curious as to how deep is this 
> problem. Are there lots of other components shipped with mozilla which 
> are effectively broken?
> Let's say I want to fix nsXmlRpcClient.js by fixing whatever is wrong 
> with latest code on the dev branch. Whom do I talk to coordinate this?

What do you mean by the "dev branch"? I would have thought that bug is 
unlikely to be fixed in Firefox 1.0.x, as that is generally only for 
security fixes.

But certainly you should be able to file a bug in bugzilla for Mozilla 
or Firefox 1.1.


More information about the Project_owners mailing list