Brian Quinlan <[EMAIL PROTECTED]> wrote: > [EMAIL PROTECTED] wrote: > > Hi Brian, > > > > XercesDocumentWrapper is the replacement class for XercesDocumentBridge. > > It's very similar, but does not support mutating the underlying Xerces DOM > > through the XalanDOM member functions. > > > > I believe we updated all of the samples to use the new class, so you might > > want to take a look at them for more information. > > I was using the result of Xerces XercesParserLiaison.createDocument() in > my XSLTResultTarget constructor (and then using the XalanDocument after > words). The createDocument() method seems to have disappeared from > XercesParserLiaison. So the suggestion is that I create my own > DOMDocument, use that in my XSLTResultTarget constructor (through > FormatterToXercesDOM), do the transformation, and then use > XercesDocumentWrapper to generate the XalanDocument that I need in the end?
The member function XercesParserLiaison::createDocument() disappeared because Xerces-C moved to a more standard way of creating Document instances, and I didn't think we needed the complexity in Xalan-C to deal with how it's done. In addition, we never supported modifying the new Xerces-C DOM through the XercesDocumentWrapper classes, so you always got a version of the Xerces-C deprecated DOM. If you're trying to transform with a Xerces-C DOMDocument as a target, you can just create the DOMDocument instance and pass it into a FormatterToXercesDOM, which you can use to construct an XSLTResultTarget. There may be some issues with this, because I'm pretty sure constructing a DOMDocument instance also creates a document Element, which you may not want. If that's the case, you will need to manipulate the Document after the transformation, to get the result you really want. Thanks! Dave --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
