|
Thank you guys,
but I did not ask how to implement this (btw, I was one of the
first who invented this trick)
I'm asking why not to implement it by xerces team, so that the
others (including me) do not bother them
with the foolish questions.
My opinion is that if (at least 10 people asking one thing)
this should be implemented.
(of course if this is reasonable)
----- Original Message -----
Sent: Thursday, April 26, 2001 4:17
PM
Subject: RE: PLEASE HELP: SAX parser
errors on validation when ValScheme=Val_Never?????
Hi Peter,
I do require to parse an xml doc that
specifies a dtd that cannot be found
(but only if validation is off) and I
have found two ways to get around it:
1. Place the doc into a
MemBufInputSource and offset the parser to begin at
the first '<' char
AFTER "<!" (this seems to work fine and is good for
performance)
2.
In resolveEntity create a dummy DTD file (again as a MemBufInputSource)
and
return that - as I am using point 1 I am yet to prove if you really need
to
write a dtd in memory that contains ONLY the DOCTYPE element of the xml
doc
or if <?xml version="1.0" encoding="something"?> will do (thanks to
Erik
for help on this))
Hope this help you - but I don't think
a critical exception should be raised
as you say (must have been done for a
reason though!)
Chris
-----Original
Message-----
From: Peter A. Volchek [mailto:[EMAIL PROTECTED]]
Sent:
26 April 2001 14:08
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject:
Re: PLEASE HELP: SAX parser errors on validation
when
ValScheme=Val_Never?????
Asking again. Are you planning to
provide a way not to throw an exception if
dtd does not exists ?
My
application strictly requires this. In the previous version (xml4c 2.3.1)
I
might to catch this exception and continue
parsing. Now, it became a
critical exception.
I know that xml rec says that if dtd is reffered
but does not exists the
document is invalid.
But no one prevent you, to
keep this by default, and provide an additional
feature, to break
this.
(it may be a method, additional parameter or just #define
variable)
Thanks for your cooperation.
-----
Original Message -----
From: Erik Rydgren <mailto:[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>
Sent: Thursday, April 26, 2001 2:06 PM
Subject: RE: PLEASE HELP: SAX
parser errors on validation when
ValScheme=Val_Never?????
Yes that
is the correct behaviour.
The DTD can contain definitions that are needed
even when not validating.
/ Erik Rydgren
-----Original
Message-----
From: Prior, Chris [mailto:[EMAIL PROTECTED]]
Sent:
den 26 april 2001 13:00
To: '[EMAIL PROTECTED]'
<mailto:'[EMAIL PROTECTED]'>
Subject: PLEASE HELP: SAX parser errors on validation
when
ValScheme=Val_Never?????
Hi all,
I am using the SAX
parser and setting validation to Val_Never, yet when I
parse an xml doc
that specifies a dtd the parser fails if it cannot find
the
dtd!!!
Why is this the case when I am not interested in
validating? Surely looking
for the dtd when no validation is required is
not correct?
Please
help!
Chris
___________________________________________________
Email
Disclaimer
This communication is for the attention of the
named
recipient only and should not be passed
on to any other person. Information
relating to
any company or security, is for information
purposes only
and should not be interpreted as
a solicitation or offer to buy or sell any
security.
The information on which this communication is based
has been
obtained from sources we believe to be reliable,
but we do not guarantee
its accuracy or completeness.
All expressions of opinion are subject to
change
without notice. All e-mail messages, and associated
attachments,
are subject to interception and monitoring for lawful business
purposes.
___________________________________________________
---------------------------------------------------------------------
To
unsubscribe, e-mail: [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>
---------------------------------------------------------------------
To
unsubscribe, e-mail: [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: [EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>
___________________________________________________
Email
Disclaimer
This communication is for the attention of the
named
recipient only and should not be passed
on to any other person. Information
relating to
any company or security, is for information
purposes only
and should not be interpreted as
a solicitation or offer to buy or sell any
security.
The information on which this communication is based
has been
obtained from sources we believe to be reliable,
but we do not guarantee
its accuracy or completeness.
All expressions of opinion are subject to
change
without notice. All e-mail messages, and associated attachments,
are subject to interception and monitoring for lawful business
purposes.
___________________________________________________
---------------------------------------------------------------------
To
unsubscribe, e-mail: [EMAIL PROTECTED]
For
additional commands, e-mail: [EMAIL PROTECTED]
|
