Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: Error loading document with processing instructions using .NET

From: "Amol Kher [MSFT]" <fundamol.spam.block@-------.--->
To: NULL
Date: 9/27/2004 2:40:00 PM
There was an error related to PI Parsing in the .NET 1.1, which version of
1.1 are you using? Either download the latest SP1 or the new Whidbey.

Thanks,
Amol

"Fernando Lopez" <fvas913@y...> wrote in message
news:ab64ba36.0409012204.5ddfd943@p......
> Hi Mike,
>
> I am getting the same error.
>
> From what I can tell the parser is lumping together 2 processing
> instructions into 1.
>
> i.e.  <? p1 ?><? p2 ?>
> The parser interprets this as one whole processing instruction with
> inner text of  "p1 ?><? p2", hence the "Cannot have '?>' inside an XML
> processing
> instruction."
>
> What I want to know is why and when it does this.
> Placing spaces at various places can make the error go away, but
> sometimes not.
> Has anyone heard of this before or know exactly what causes it?
>
> Thanks
>
> Fernando
>
>
>
>
>
>
>
>
> "Mike Lansdaal" <michael.t.lansdaal@b...> wrote in message
news:<OdbseV3jEHA.592@T...>...
> > More data on this:
> >
> > 1) Changing the length of the data in the <title> tag of the <table>
will
> > cause the parser to fail in either <tablerow> 16 or 18.
> > 2) Adding or deleting a single character in the processing instruction
of
> > the node where the failure occurs can cause the parser to parse
correctly.
> > 3) When the parser fails, it reports a row as having 35 child nodes,
instead
> > of 37.
> > 4) Extracting just the <tablerow> where the parser fails and trying to
load
> > that snippet always loads fine.
> >
> > 4) Documents that fail to load with System.XML will load correctly when
> > using MSXML4 library.
> >
> >
> > "Mike Lansdaal" <michael.t.lansdaal@b...> wrote in message
> > news:%23ty48$sjEHA.3944@t......
> > > I am getting an error "Cannot have '?>' inside an XML processing
> > > instruction." when accessing the innerXML property of a document (I'm
> >  using
> > > C# to load the document). The error disappears if the file is editted
to
> > > insert line breaks (just load and save in XMLSpy or if I use a text
editor
> > > and manally insert line breaks) or even change the text size by a
single
> > > character.  As a workaround, this can be done programmatically, but
does
> >  not
> > > address the underlying problem.
> > >
> > > The structure of the particular section where the error is being
reported
> > > (in this large XML file) is:
> > >
> > > <tablerow rht="15.00px">
> > > <cellrule rty="-"/>
> > > <tablecell chj="c" cvj="t" shd="0"><?Pub _cellfont
> > > TypeSize="9pt"?>19</tablecell>
> > > <cellrule rty="-"/>
> > >
> > > etc....
> > >
> > > </tablerow>
> > >
> > > The exception is thrown for each <tablecell> of a particular row - not
for
> > > the cells in prior or successive rows. I can not spot broken or
malformed
> > > tags when looking at the raw data in an editor, nor does there appear
to
> >  be
> > > any non-printing characters when I view with a binary file editor.
> > >
> > > Any thoughts?
> > >
> > > Thanks, Mike Lansdaal
> > >
> > >
> > >
> > >




transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent