RE: XML Toolkit concatenating strings on multiple calls

Maybe I didn't make this as clear as I should have.

The read from the data queue is not causing concatenation that is fine. It is the creation of the XML string using the toolkit that results in concatenation. The result of building the XML string for each iteration returns a string containing every XML string created up to that point.

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-
bounces@xxxxxxxxxxxx] On Behalf Of Pete Hall
Sent: Tuesday, October 04, 2011 6:06 PM
To: rpg400-l@xxxxxxxxxxxx
Subject: Re: XML Toolkit concatenating strings on multiple calls

On Tue, 04 Oct 2011 17:11:08 -0500, Rick.Chevalier wrote:

I am using the XML Toolkit 5.6(?) to create an XML string. The
program is processing entries from a data queue until the queue is
empty. The XML is being formed properly but the resulting string is
being concatenated to the previous result. For example, if there are
three entries on the queue I will get the correct XML string on the
first call, the correct XML for the second entry appended to the first
XML string on the second call, and the correct XML for the third entry
appended to the XML string containing the first two entries on the
third call.

I've not had that problem. I'm using a construct like this:
xmlData = "";
KeyedDataQueue dq = new KeyedDataQueue(iHost, pathToQueue);
DataQueueEntry dqe = null; do {
dqe = dq.read(dataQueueKey, 1, "EQ");
if (dqe != null) xmlData += dqe.getString(); } while(dqe != null);
dataExists = (xmlData.length() > 0);

hth
--
Pete Hall
pete@xxxxxxxxxxxxxx
--
This is the RPG programming on the IBM i / System i (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.

Privileged and Confidential. This e-mail, and any attachments there to, is intended only for use by the addressee(s) named herein and may contain privileged or confidential information. If you have received this e-mail in error, please notify me immediately by a return e-mail and delete this e-mail. You are hereby notified that any dissemination, distribution or copying of this e-mail and/or any attachments thereto, is strictly prohibited.