Andy Clark wrote: > > Xerces2 doesn't have a StringPool, so String objects are passed > to the native interfaces. Both Xerces 1.x and Xerces2 have > internal interfaces but at least we're trying to "standardize" > the interfaces in Xerces2 (this is what we call XNI). > > In both versions, you can directly extend the DOMParser class > and override the appropriate method to get the information > that you need. In Xerces 1.x, you'll have to turn the ints > into String objects by calling the StringPool: > > String s = fStringPool.toString(i); > > But in Xerces2, you'll just get the String object directly.
Is there a reason both versions of DOMParser, as well as org.apache.xerces.xni.XMLDTDHandler don't use org.xml.sax.ext.DeclHandler? The methods seem to have the same masks... The alternative would be to go with a SAX parser, but then we'd have to rewrite all Document.createXxx() calls, which looks like a waste. Ari. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
