In my opinion one advantage of the entity resolver is the ability to pass
in the grammar direct as a stream.
But using precompiled grammars sounds still better.
About my proposing:
The method description does not allow the resolving of grammar URIs.
The class description allows it. So what I meant is switching between
grammar URI resolving
enabled or not. At the time it seems to be not enabled.
In SGML it is a common and well proven technic only to use the PUBLIC
identifier to reference the grammar.
In my opinion the EntityResolver class extends and implements this concept
for the use with Java IO objects
(but unfortunately only by the class description.)
Regards
Thomas
Andy Clark <[EMAIL PROTECTED]> am 04.07.2001 03:51:25
Bitte antworten an [EMAIL PROTECTED]
An: [EMAIL PROTECTED]
Kopie:
Thema: Re: Entity Resolver and Xerces 1.4.1
[EMAIL PROTECTED] wrote:
> This is in contrast to the method description of resolveEntity():
It doesn't seem to be in contrast. Just not as complete a
comment as in the SAX JavaDoc.
> In my opinion the first one should be the right one to allow
> storing grammars in the database also.
eh? Are you referring to grammar caching?
I don't believe that we have plans to try to implement
grammar caching in Xerces 1.x. This is definitely something
for Xerces2. But I have an idea to have a separate interface
to query pre-compiled, cached grammars without using the
EntityResolver. In fact I think that the EntityResolver is
the wrong thing to use anyway.
There are two primary ways to associate a grammar (or
grammars) to an instance document: 1) by the name of
the root element, and 2) by the namespace of the
element/attribute.
> So what do you think about a property to switch between this
> two options until this contradiction is fixed?
What two options are you proposing? I don't see the
difference, yet.
--
Andy Clark * IBM, TRL - Japan * [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
