Hi Dave,
I've used some simple workarounds to "make a copy" of a node. So, while
not cloning the node per say, in my case a copy was "good enough".
Perhaps it might be for you?
Mind, this uses an exslt function (which xalan-j supports of course).
e.g.:
http://www.w3.org/1999/XSL/Transform";
Internally, Xalan uses a read-only data model (the DTM), which is has a
read-only DOM adapter layer wrapped around it when nodes are passed to
extension functions. The cloneNode operation, because it creates a new
node in the same Document as the original node, would break the read-only
behavio
