×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Anyone know if there is a way to get more information about a parse
error when jt400 is processing a PCML file?
Right now it's being extraordinarily uninformative ...
Element type "data" must be followed by either attribute
specifications, ">" or "/>".
1 error detected parsing pcml document.
Um, thanks program ... how about the LINE that caused the error? Maybe
the context?
I've tried turning on the PCML Trace, but it doesn't add anything.
The PcmlException contains no useful information.
I tried rebuilding jt400 so I could debug it ... and that helped, to an
extent.
The error was coming from PcmlSAXParser constructor ... where it was
trying to parse the PCML ... a SAXException was being thrown. Oddly
enough, the SAXException contained line & column information for the
error. Unfortunately, the line & column information was completely
wrong. It was reporting that the error was occurring on line 460 column
68 ... but the PCML file only had 435 lines.
I found the error ... it was a simple typo (which I expected ... instead
of a single double quote ("), I had two double quotes ("") in an
attribute value.
Sure would be nice if the parser could give useful and accurate parse
error information.
Thanks!
david
midrange.com
