[EMAIL PROTECTED] wrote: > it might be a good time to bring up once again an issue that took a > lot of bandwidth in the summer but was never resolved--what should > grammar caching in Xerces2 look like? > > [SNIP]
Neil, thanks for such a detailed posting. I think you've captured the problems with a decent solution, as well. Of course, as always, I have some tweaks to suggest. :) You introduce an interface called XMLGrammarDescription which is actually more like an XMLLocator (sans the row and column info). And then you proceed to use it in a modified XMLEntityResolver interface. If it's going to be a generic locator, of sorts, then I think we should definitely change the name to indicate its more general purpose. (As a side note, we should try to keep the method names in line with our existing naming scheme.) Since we need a resolver for both entities and for locating grammars, perhaps we should define a more generic location interface in the core XNI that would then be used by the entity resolver interface. It could then be extended for use by the grammar resolution mechanism. But I need to ask if you have a solution for the grammar resolver needs access to the entity resolver problem? The DTDDescription interface has a method called "getEntityName". The documentation states that this method can return the root element name *or* the name of an entity declaration. If the method serves this dual purpose then the name is wrong. I don't have an alternate suggestion at the moment, though, but we should change it. The rest seems fine; I just have a few minor naming nits. -- Andy Clark * [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
