I'm just curious and maybe missing something, but the suggested solution is
instead of having the software package encode the & character, it's to make
the contents of the container as CDATA so that no encoding is needed?

Or was the intention of this XML package that you need to encode the data
yourself?

Brad
www.bvstools.com

On Tue, Dec 15, 2015 at 11:54 AM, Richard Schoen <
Richard.Schoen@xxxxxxxxxxxxxxx> wrote:

Nope, missed that first one, but I think I understand what to try.

I would rather not make any actual changes to XMLSERVICE since it's
already used in its current form by Zend and other.

This should hopefully resolve the issue.

Regards,

Richard Schoen | Director of Document Management Technologies, HelpSystems
T: + 1 952-486-6802
RJS Software Systems | A Division of HelpSystems
richard.schoen@xxxxxxxxxxxxxxx
www.rjssoftware.com
Visit me on: Twitter | LinkedIn

------------------------------

message: 5
date: Tue, 15 Dec 2015 08:24:15 -0600
from: Aaron Bartell <aaronbartell@xxxxxxxxx>
subject: Re: XMLSERVICE and Parsing XML Responses

Richard, did you see my response?
http://archive.midrange.com/midrange-l/201512/msg00401.html

You need to specify the cdata option to be "on" so responses will be
enclosed in a CDATA tag (character data), telling the parser not to attempt
to parse it.

<data><![CDATA[A & E Services]]></data>


?Thanks,?
Aaron Bartell
litmis.com - Services for open source on IBM i


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.



This thread ...

Replies:

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

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