OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
Re: [xml-dev] Error and Fatal Error

By the way, I don't know why the tools used don't do the escaping
but might be that they weren't expecting the input data to end up
in XML (which would be ironic since they are based on Ajax).
I think the tools used are simply (and typically for .NET) an AJAX
grid (probably a Telerik RadGrid) passing data to a .NET dataset
on the server side. The XML might therefore be to some extent
determined by a combination of the user's input (illegal characters
perhaps included, like '&' and '<' though it is mainly '&' causing
problems) and the AJAX/mainstream tools/controls. Then the
XML is sent to the parser. We could try first parsing it as text to
catch the illegal characters but this way will be XML-ignorant
and we prefer to use a tool which 'understands' XML so we can
concentrate the coding efforts on the element content and abstract
away the angle brackets. It really should all 'just'work'.
Stephen D Green

On 17 July 2011 20:30, Stephen D Green <stephengreenubl@gmail.com> wrote:

On 17 July 2011 19:34, Chris Burdess <dog@bluezoo.org> wrote:
So you're creating not-well-formed XML yourself and then complaining that XML parsers don't process it?

It's a little hard to have sympathy with your viewpoint in that case. Why don't you just create well-formed XML instead?

because the XML content includes data input into textbox controls, etc
in a webpage and we do not want to prevent users inputing '<' and '&'
Stephen D Green

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]

News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 1993-2007 XML.org. This site is hosted by OASIS