On Wed, Oct 08, 2003 at 01:41:33AM -0500, Mike Pilato wrote:
> "C. Michael Pilato" <cmpilato@collab.net> writes:
>
> > "C. Michael Pilato" <cmpilato@collab.net> writes:
> >
> > > It would appear that in neon 0.24.3, the error is never left NULL, but
> > > is instead initialized to "Unknown error". There must, then, be some
> > > other way to check for an errorful state. Now... where is that
> > > booger...
> >
> > A-ha! We should be calling ne_xml_valid(), and only if the XML was
> > invalid should we try to fetch the error. Testing a patch now.
>
> Okay, well, this turned out to be trickier than I thought.
If I understand this correctly: the issue is that ra_dav needs to be
able to distinguish between an error from the XML parser itself and an
error which occurs when ra_dav's SAX callbacks return a <0 value.
There's never been a way to do this in the neon API, though it's a
definitely a reasonable feature to have. I'd recommend limiting SVN to
using 0.24.[0-2] and working out how to add this to neon rather than
performing major surgery on ra_dav (I expect the latter would be more
work than the former).
joe
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Oct 8 10:57:28 2003