Andy Clark wrote: > > "K. Ari Krupnikov" wrote: > > 1) add a constructor that takes a DOMImplementation argument and > > overload init() and reset(). In this case, > > I like this solution. Either a constructor or having a > property for the DOMImplementation object works for me. > Perhaps the second is better because people create their > parsers from JAXP and have no way of passing arguments > to the constructor. Unfortunately, though, JAXP doesn't > have an extensive feature/property mechanism for DOM as > it does for SAX -- so we're back to creating the parser > object directly, anyway... <sigh/>
Directly as in with no arguments from the user, not as in newInstance()! That makes all the difference in the world :=) > > I can patch DOMParser if there is interest in these solutions. It appers > > that changes would be limited to org.apache.xerces.parsers.DOMParser > > Patches for new features as well as bug fixes are always > accepted. :) I'll see what I can do! -- K. Ari Krupnikov DBDOM - bridging XML and relational databases http://www.iter.co.il
