David,
I had a quick look. Assuming a new createDOMDocument method was created which created a XalanDocument based on a DOMDocument (rather than DOM_Document which is what the current method calls) - I think there is still a problem in that the FormatterToDOM calls appendChild - which in the wrapper classes will throw a NO_MODIFICATION_ALLOWED_ERR exception.
My reading is that fixing this will require the Wrapper classes be updated to allow modification?
Cheers, Berin
Colin Paul Adams wrote:
"David" == David N Bertoni/Cambridge/IBM <[EMAIL PROTECTED]> writes:
David> Could you also include a small code snippet, so we can David> reproduce it?
I don't know about ALSO - I see there is no selection for reporting bugs against the CVS code.
Here is my snippet (source and sheet are pointers to XSLTInputSources):
XercesParserLiaison the_parser_liaison; XalanDocument * document_result = the_parser_liaison.createDocument();
XSLTResultTarget target ( document_result );
int result = xalan.transform ( *source, *sheet, target );
XalanElement * element = document_result->getDocumentElement(); std::cerr << "Document element is " << element << ", " << XMLString::transcode ( element->getNodeName().c_str() ) << std::endl;
The above code outputs the document element's node name correctly, as generated by the transform.
const DOMDocument * dom_result = the_parser_liaison.mapToXercesDocument( document_result );
dom_result now has the value 0;
