Hi all,
I did not log it as a bug yet. I found a problem in my code that allowed the
2 XmlDecls to be in the response.
I have not had time to try and do a degenerate case to verify that this is a problem
in XML-RPC or not.
Thanks
Rick
On Tuesday 19 February 2002 16:05, Daniel Rall wrote:
> "John Wilson" <[EMAIL PROTECTED]> writes:
> > Null is a non standard extension to XML-RPC. Hannes used to support it
> > but removed it when Dave Winer (who owns the spec) voiced his disapproval
> > of the extension.
> >
> > I think that the code may have a problem with this situation. I spent
> > some time working with Rick Blair on a similar point.
> >
> > I think that the server returns something like
> >
> > <?xml version="1.0"?>
> > <methodResponse>
> > <params>
> > <param>
> > <value>
> > <?xml version="1.0"?>
> > <methodResponse>
> > <fault>
> > <value>
> > <struct>
> > <member>
> > <name>faultString</name>
> > <value><string>java.lang.RuntimeException: null value not
> > supported by XML-RPC</string></value>
> > </member>
> > <member>
> > <name>faultCode</name>
> > <value><int>0</int></value>
> > </member>
> > </struct>
> > </value>
> > </fault>
> > </methodResponse>
> >
> > Which is obviously wrong. Rick was going to report it as a bug but he has
> > yet to do so, so I will;)
> >
> > I was going to test this and offer a patch but I'm afraid I a bit pressed
> > for time at the moment.
>
> If you don't have time to patch it, logging an issue at
> http://nagoya.apache.org/bugzilla/ would be a big help.
