Sounds like maybe it's a parser bug. Perhaps we need to separate out
setting schema processing from validaton, although may become a source for
user errors.
I'll ask the parser folks if this is the intended behavior.
Dave
Brian Quinlan
<brian@sweetapp. To: [EMAIL PROTECTED]
com> cc: (bcc: David N
Bertoni/Cambridge/IBM)
Subject: RE: Schema question
09/22/2002 08:29
PM
Please respond
to xalan-dev
> The parser would be handling that, so I'm not sure. Unless your
document
> contains a schema hint, I wonder why it would even try.
> Some of our tests contain DTDs, and we run with validation enabled,
and I
> haven't noticed anything strange. What are you seeing?
I'm seeing this problem is two places:
1. The ErrorHandler (both mine and the default) is displaying an extra
warning:
An exception occurred! Type:RuntimeException, Message:Warning: The
primary document entity could not be opened. Id=
2. If an EntityResolver is installed, it is asked to resolve an entity
with a null system and public id string
I've verified that this comes from an attempt to load the schema by
examining the stack during a call to the ErrorHandler. The spurious
warning is particularly annoying (though I will have to change the logic
in my EntityResolver to accommodate this as well).
Cheers,
Brian
- Re: Schema question David N Bertoni/Cambridge/IBM
- RE: Schema question Brian Quinlan
- RE: Schema question Brian Quinlan
- RE: Schema question David N Bertoni/Cambridge/IBM
- RE: Schema question Brian Quinlan
