Your & needs to be replaced with &amp like an apostrophe needs to bereplaced with &apos.
I use an RPG program to scan all text strings and rebuild with the required XML codes.

On Tuesday, 15 December 2015, 4:18, Bradley Stone <bvstone@xxxxxxxxx> wrote:

The & should be encoded.  Your parser is looking for the representation
following it and hits a blank...  error.

I run into this all the time with XML and different trading partners.
There's never one that works like the other, or that doesn't need special
attention and data "massaging" before I can run it through a parser.



On Mon, Dec 14, 2015 at 4:32 PM, Richard Schoen <
Richard.Schoen@xxxxxxxxxxxxxxx> wrote:

Not sure if this is specific to .Net, but when parsing returned XMLSERVICE
XML data that contains an ampersand.

Example:  "A & E Services"  I get a .Net XML parser error.

If I replace the ampersand with something else it works fine.

Has anyone else seen this issue with XMLSERVICE or even parsing data that
contains special characters that aren't encoded ?

Any thoughts appreciated.



Richard Schoen | Director of Document Management Technologies, HelpSystems
T: + 1 952-486-6802
RJS Software Systems | A Division of HelpSystems
Visit me on: Twitter<https://twitter.com/richardschoen> | LinkedIn<

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


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

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