So you're saying it shouldn't escape the & character when not in CDATA?

I just want to be clear for the thread.

Brad
www.bvstools.com

On Tue, Dec 15, 2015 at 10:06 PM, Aaron Bartell <aaronbartell@xxxxxxxxx>
wrote:

Cdata is correct, acceptable, and not a bandaid.

XMLSERVICE is not new and is definitely used in production.
On Dec 15, 2015 10:03 PM, "Bradley Stone" <bvstone@xxxxxxxxx> wrote:

Why doesn't it escape the & character, though.. that's my question. It's
pretty well known that unless in CDATA what follows & is an entity
defining
a special character.

Don't just go for a quick bandaid. If this product really doesn't
escape &
I'd question if it's really been used in production at all.

Aaron's suggestion of putting it in CDATA "should" work.. but that
doesn't
mean it's correct.

Brad
www.bvstools.com

On Tue, Dec 15, 2015 at 8:40 PM, Richard Schoen <
Richard.Schoen@xxxxxxxxxxxxxxx> wrote:

I'll report back after I test Aaron's tip.

I know I can modify XMLSERVICE as well as other open source, but since
XMLSERVICE is being widely deployed and even as part of OS updates that
would not be my first choice which is why I posted here.

I figured it was some of my XML ignorance causing me issues :-)

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: 1
date: Tue, 15 Dec 2015 16:52:52 -0500
from: Jon Paris <jon.paris@xxxxxxxxxxxxxx>
subject: Re: XMLSERVICE and Parsing XML Responses

I believe that both Aaron and Charles have pointed you to the
documentation that deals with your issue.

I was merely pointing out at the time that if you perceive a flaw then
you
can fix it - there was no need to hack _around_ it.

I did, and still believe, that XMLSERVICE is production ready - but I
never said it was perfect.


On Dec 15, 2015, at 11:48 AM, Richard Schoen <
richard@xxxxxxxxxxxxxxxxx>
wrote:

There is that :-)

However one would think if guys like Zend, Mike Pavlak and Jon Paris
are promoting its use it is already production ready so why should I
need to tweak it.

Maybe Zend has done their own hacks ?

Regards,

Richard Schoen
RichardSchoen.Net
Cell: 612-384-2118
------------------------------

message: 3
date: Tue, 15 Dec 2015 10:11:49 -0500
from: Jon Paris <jon.paris@xxxxxxxxxxxxxx>
subject: Re: XMLSERVICE and Parsing XML Responses

XMLSERVICE is Open Source Richard.

If you think it needs fixing why not fix it instead of hacking around
it?





--
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 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 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-Ups:
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].