|
Hello,
I'm having a problem with the importNode()
function...I'm calling it with the "deep" option set, and but I'm finding ?that
for some of the nested children, the attribute values aren't being copied over.
so, printing the node out before importing I
get:
<View><MetaLink>http://www.geoviz.com</MetaLink><ResourceIDs><ResourceID id="1"/><ResourceID id="7"/></ResourceIDs><EyePoints/></View> but printing the node out after importing, I get: <View><MetaLink>http://www.geoviz.com</MetaLink><ResourceIDs><ResourceID id=""/><ResourceID id=""/></ResourceIDs><EyePoints/></View> So that the whole node structure copies over..but the attribute values of the ResourceID elements are not being copied over. Now, I actually create this node structure from a
String in the first place, and
I've found out some more information from a
previous poster:
Jeff Greif [EMAIL PROTECTED]
wrote:
>But some implementations have a quirk (bug!) in importNode such that it
will
>produce a bad document when the imported node was built by a different >parser from that of the importing document. I think I ran into this in a >situation where the importing document was built by xerces PSVI DOM (I can't >remember which version, probably 2.1.0) and the imported node was built by >the Crimson parser. So perhaps the problem is in the way I'm creating
my document. Does Xalan have a method where I can parse a String and turn it
into a Node, Document or DocumentFragment? Whats the best way to go about doing
this?
Currently I'm using:
createDocumentBuilder().parse( new InputSource(new StringReader(string)));to parse the string and create a new document. Is there a better way to do this that will cause Xalan to import the Node structure with no problems? Thanks for any help you may be able to give, Claire
|
