Re: Validated parsing: when grammar is found, the entity resolver is not
calle 2003-02-14 - By sandygao@(protected)
It's not likely that we'll change the behavior, but what you want can be
achieved without such change.
When the grammar is found in the grammar bucket, we have to use it, because
that's loaded when the current instance document is parsed, and (by your
definition) belongs to that instance.
For the case where the grammar is found in the grammar pool, you can
implement your own grammar pool, and return the proper grammar when
getGrammar is called. (You can even call your entity resolver from within
the grammar pool, if you want to.)
Cheers,
Sandy Gao
Software Developer, IBM Canada
(1-905) 413-3255
sandygao@(protected)
"Carla Spruit"
<carla@(protected) To: <xerces-j-user@(protected)
.apache.org>
> cc:
Subject: Validated parsing:
when grammar is found, the entity resolver is not
02/14/2003 11:58 called
AM
Please respond to
xerces-j-user
Hi,
My question concerns validated parsing with an entity resolver and a
grammar pool.
The schema validator identifies a schema grammar by its target
namespace. When the validator finds a grammar with this target namespace
in the grammar bucket or in the grammar pool, the entity resolver is no
longer called.
I know this is not a bug and I can understand that the validator skips
the entity resolver to enhance performance, however I would prefer the
entity resolver to be called as it would give me more control during
validated parsing.
One of the reasons I would like more control is that I want to prevent
the validator to use a grammar that does not belong to the document
being validated, even though it has the same target namespace.
Especially in cases where the target namespace is null, this is likely
to happen.
Is there any chance that you change this behaviour in the future?
Thanks in advance!
Carla Spruit
X-Hive Corporation (www.x-hive.com)
email: carla@(protected)
phone: +31 010 2818080
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-user-unsubscribe@(protected)
For additional commands, e-mail: xerces-j-user-help@(protected)
---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-user-unsubscribe@(protected)
For additional commands, e-mail: xerces-j-user-help@(protected)
|
|
