On Tue, 2002-01-08 at 12:25, [EMAIL PROTECTED] wrote: > > Conceptually, the flow would look something like this: An application > instantiates a certain parser Configuration, and associates its > GrammmarPool implemntation as a property of thatConfiguration. When a > Validator object in the configuration begins to validate, it requests > that a bucket of grammars of the appropriate kind be filled by the > GrammarPool. As it parses, the Validator takes grammars from the > bucket if it can, then gives the GrammarPool a chance to prvide the > grammar if it wishes, then the XMLEntityResolver gets a chance to > resolve the request to a file of the appropriate type. At both these > stages, as much information is provided to the GrammarPool and the > XMLEntityResolver as is likely to prove at all helpful in identifying > the appropriate resource. At the conclusion of parsing, the validator > will make available the contents of its bucket to the GrammarPool, > which can then determine whether to incorporate the grammars or ignore > them. I tend to be of the view that parsing should be aborted with a > fatalError if something goes wrong in the grammar retrieval > process--e.g., if the GrammarPool gives a Validator a grammar of the > wrong type--but this is certainly a thorny and multifaceted question.
I assume that there is a default GrammarPool implementation per parser configuration. How does an application store a grammar pool so that it can avoid re-creating one? How can an application create a grammar pool that is locked to a particular set of grammars? Is a grammar pool sharable amongs multiple parser instances? Ted --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
