I've been working on performance, and I've noticed that in fact the start/endPrefixMapping calls are redundant in the XNI pipeline: the information about namespace binding can be retrieved via a namespace-context property (currently it is internal property but can be made public) that holds xerces.xni.NamespaceContext object. This object is *live*, since it is updated if new namespace declaration was read, and allows to query local namespace declarations.
I've prototyped this in Xerces and have seen 0%-6% performance improvement depending on the content of the file, i.e. if no namespace declarations were found, obviously, there is no performance gain. However, if there are many namespace declarations and file size is 32K and larger you would start seeing performance gain. So .. I propose to remove start/endPrefixMapping methods from the xerces.xni.XMLDocumentHandler interface. Comments? -- Elena Litani / IBM Toronto --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
