Hi Urs,
Urs Reupke wrote:
> I suspect that the 'quickest' thing to do would be to deep clone the
> dom4j generated SVG Document into another SVG Document (this should
> fix the attribute weirdness).
I have already tried to quickfix the problem by deep cloning, as you
told me to (using DocumentUtils.deepCloneDocument with my document and
the Batik SVGDomImplementation), but to no avail - the
ElementsByID-Table stays 'null'.
Gahh, the deepCloneDocument call simply copies the 'weird'
Attribute child nodes and so it fails in the same way.
I am fairly certain that adding:
result.setNodeValue(importedNode.getNodeValue());
return result;
To the ATTRIBUTE_NODE case of the importNode method of
batik.dom.AbstractDocument (around line 280). Will make the
clone method work.
We will explore the other option, but it will probably take some days
until we can tend to this. I will report to the list when and how we
solved the problem, if we'll be able to.
I will also try and look at this in the coming days.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
