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/> > > > http://apache.org/xml/properties/dom/document-class-name doesn't need to > > be set explicitly - it can be established at runtime, and probably isn't > > needed at all, since you can call a standard factory method instead of > > newInstance() > > For backward compatibility, though, I wouldn't remove this > property. Perhaps as we move to Xerces2, we can remove it > there and rely on the DOMImplementation object instead. > > > 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. :)
A stupid question - which cvs tag should I patch against? -- K. Ari Krupnikov DBDOM - bridging XML and relational databases http://www.iter.co.il --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
