Thanks for the response, Joe. Actually, in a previous message, I discussed trying to do our own cloner, but there also appears to be an issue with the NodeList returned from getChildNodes() on a DTMNodeProxy object. Kinda up the creek sans paddle on this one...
- Rick -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] Sent: Tuesday, November 13, 2001 11:49 AM To: [EMAIL PROTECTED] Subject: Re: Xalan D13/Extension Function Issue? The import appears to be failing because their implementation of importNode is calling getDOMImplementation(), and our DOM proxy doesn't currently support that operation. We can add it. It ought to be relatively low risk, but I'm not sure whether it's critical enough to add during he D13 stable period. Workaround, in the meantime, would be to use one of the many user-level DOM-tree cloners written before importNode() was added to the DOM. You could even swipe the logic out of Xerces' implementation of cloneNode. I'll log this into Bugzilla so we don't forget it, but I'm not sure what priority to give it.
