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



Jon,

I've looked at it, I understand what it's giving you...

I realize it doesn't give you a string you can just concat into a buffer.

But couldn't you _rebuild_ the input XML string one piece at a time from
the information provided?

when event = *XML_START_ELEMENT;
buffer += '<' + %subst(chars : 1 : stringLen);
when event = *XML_END_ELEMENT;
buffer += '</' + %subst(chars : 1 : stringLen) + '>';

Non trivial for sure. And you probably couldn't get an exact copy of the
input XML. But the result should certainly parse the same..

Rather XML-INTO would be easier or not would depend on the structure of the
XML you are trying to extract I think.

Charles

On Wed, Nov 4, 2015 at 12:20 PM, Jon Paris <jon.paris@xxxxxxxxxxxxxx> wrote:

You’ll have to look at XML-SAX Charles.

You _cannot_ do what you are suggesting with XML-SAX because what XML_SAX
passes its handler is: A code to indicate the type of data (basically
beginning of a specific attribute or element name, end of same, etc.), the
actual name of the item found or the data for the element/attribute. As you
can see - there is no way there to get the XML string - it has already been
parsed out into its components.


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.


Jon Paris

www.partner400.com
www.SystemiDeveloper.com

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

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.