XML issue in XE
XML issue in XE
We have an issue which seems very strange. We use it for processing a return call from an external service (WorldPay in the most immediate case). It seems that everything that was compiled before December 19th (maybe a little later) handles the returned XML without a problem. Anything that has been compiled recently fails to load the XML. It may had a problem with $#A characters (adding them in when we created xml and not handling them when loading. This helped with some apps but even when we took those out and it still had a problem. It seemed to have a problem loading with this as part of the document
http://dtd.worldpay.com/paymentService_v1.dtd">
once I took that out it was fine.
I haven't updated anything within my XE for sometime.
Any ideas?
We have an issue which seems very strange. We use it for processing a return call from an external service (WorldPay in the most immediate case). It seems that everything that was compiled before December 19th (maybe a little later) handles the returned XML without a problem. Anything that has been compiled recently fails to load the XML. It may had a problem with $#A characters (adding them in when we created xml and not handling them when loading. This helped with some apps but even when we took those out and it still had a problem. It seemed to have a problem loading with this as part of the document
http://dtd.worldpay.com/paymentService_v1.dtd">
once I took that out it was fine.
I haven't updated anything within my XE for sometime.
Any ideas?
If anybody's got a clue, I am interested in the issue, too :)
ReplyDeleteglad it's not just me
ReplyDeleteOh no, it IS just you :)
ReplyDeleteI am interested simply because I do quite a bit of XML stuff - and this sounds like something I better keep an eye on.
A
Does the .dtd validate correctly?
ReplyDeleterunning the xml against an external validator says it is all ok.
ReplyDeleteIs the site with the .dtd accessible from where the xml is processed, i.e. your app is not running without access to the .dtd site?
ReplyDeleteIs there any exception handling around reading the DLL which can catch issues, or events that can be monitored for debug info?
ReplyDeleteThe dtd is accessible from the computer. If run an application compiled on or before December 19th the xml is handled without a problem. Anything compiled since Christmas (even without changes to the code) rejects the xml. Not much in the way of debugging as it happens once the XML is handed across to the MSXML library
ReplyDeleteSo if you take the source from a version before xmas, and compile, and deploy to a site that have the working version - it stops working?
ReplyDeleteIf you take the old .exe and run locally - it works?
That must indicate some change in your development environment somehow. Any updates of libs or component packs installed since christmas? Any new .tlb's generated?
That's pretty much it Lars. Something must have changed, but no components have been updated. I thought a windows update to MSXMLx might have been the issue but they haven't been modified either. All very weird.
ReplyDeleteWasn't DTD support disabled by default in MSXML some time ago? Or 'resolveExternals' set to false by default, whereas it was previously true by default?
ReplyDelete