-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

That sounds like mismatched element tokens. I get little nasties like
that sometimes. If you insert a linefeed immediately ahead of each "<"
character, all you need to do is find the line that does NOT end with
">" Textpad is very good at that.

Or you can write a little awk script very easily - something like:

BEGIN {
RS=">|>\n|>\r\n"
}
/ *<.*</ {
print(NR "\t" $0 ">")
}

It will output the record number (or at least the number of preceding
">" characters) followed by the offending text. Awk is a very useful
little scripting language for stuff like this. It's part of the gnu
software project, so you can download it for free. It's included in most
Linux distros, but it's also available for Windoz. There are a couple of
dependencies (also free) If you're interested, I can fill you in on
exactly what they are.

Pete Hall
pbhall@xxxxxxxxxxxxx
http://pbhall.us


David Gibbs wrote:
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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHBEQHpcZsDl8OX6kRAkAWAJ9Qqf09s5klmYBx+NfJliOawvOqYgCghxtf
LmWoswvSD3yedXreYh0kPkQ=
=LOss
-----END PGP SIGNATURE-----

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.