|
On Nov 4, 2015, at 10:20 AM, Charles Wilt <charles.wilt@xxxxxxxxx> wrote:
On Wed, Nov 4, 2015 at 9:34 AM, Jon Paris <jon.paris@xxxxxxxxxxxxxx> wrote:
Doesn’t help.
XML-SAX will break out the components (element name and element data) just
the same as XML-INTO does. Only difference is it does it one field at a
time. Not helpful for the OP.
I can think of a risky non-guaranteed strategy where XML-SAX might help -
but it relies on the compiler internals remaining consistent and I
certainly wouldn’t want to base production code on it - a one-time routine
maybe.
Jon,
I'll admit to not having used XML-SAX...
However, it would seem to me that it'd be easier to build a string
containing a subset of the XML from within the XML-SAX handler.
At least then you don't have to worry about the structure of the subset
data.
Though the handler might be a bit complex...since you'd have to rebuild the
string one event / data at a time.
Charles
--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.
As an Amazon Associate we earn from qualifying purchases.
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.