Don't supposed anybody has built a command line wrapper for EXPAT?

[Charles Wilt <charles.wilt@xxxxxxxxx>]

All,

Getting an XML parse error at the very end of an XML document we are
receiving with HTTPAPI...

SetError() #66: XML parse failed at line 1, col 34167: junk after
document element
Return: XML parse failed at line 1, col 34167: junk after document element

The XML is 34167 bytes long...

I can check it with an online validator and it passes...

I'm thinking there's a error in our code, probably the doc lenght, but
I'd like to manually extract the XML and run it through EXPAT
directly...

The error is in an inner XML doc...meaning that the web service
returns a XML with an base64 encoded inner XML doc, that we decode and
pass to EXPAT to parse...

I've manually extracted the base64, decoded via an online tool and
looked at the resulting XML...it looks fine.  The only thing we
noticed is that the XML we are failing on has a <Name><![CDATA[PEPE'S
TACO]]></Name> whereas other XML we don't have a problem with don't
use CDATA.

Browsing though the EXPAT source, it appears it should handle
CDATA....but I'd like to confirm with my manually extracted XML...

Thanks!
Charles
-----------------------------------------------------------------------
This is the FTPAPI mailing list.  To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------