× 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.


  1.  Home
  2. RPG400-L
  3. July 2017

Re: XML-SAX *XML_EXCEPTION event and reported parsed length question


I was under the impression it wouldn't work. Maybe that
impression was mistaken?


It's a suggestion for Vern to try.



What happens to characters that are not
representable in the target CCSID?


I'm not sure. I think it would replace the EMOJI with something acceptable
to the parser. It would be worth a try.

I suspect that XML parsers load entire documents into memory, and build a
tree structure that references each element, attribute, etc. That would be
required for validation.

Then, if the document is valid, some sort of API can be used to extract
all, or a filtered selection of content. Different parsers expose different
APIs, and different capabilities.

I admit that extracting XML content into an SQL cursor might be precisely
what one needs. In other cases, the developer may need to look at each
element, attribute, etc. separately.

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 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.