Don't ever do that. A fundamental principle of XSLT is that the source
tree is immutable. By changing the tree during a transformation you risk
confusing the processor. There is no attempt during processing to detect
changes to the tree -- in fact, the assumption everywhere is that the tree
_cannot_ change.
At any rate, I've no idea how, within a transformation, you'd even get
access to the the original input DOM, since it's wrapped in the DTM. If,
somehow, something external to the processor might change the tree, you
need to prevent that from happening.
Dave
Tobias McNulty
<[EMAIL PROTECTED] To: [EMAIL PROTECTED]
sk.com> cc: John Capehart <[EMAIL
PROTECTED]>, [EMAIL PROTECTED], (bcc: David N
Bertoni/Cambridge/IBM)
03/22/2002 12:46 Subject: Modifications during a
transformation
PM
What happens if you modify a Xerces DOM from within a Xalan
transformation (in the same thread, while Xalan is running the
transform)? Is it synchronized such that it will produce a deadlock,
will the new changes be available to Xalan, or will the changes be
delayed until the transformation finishes?
Thanks,
Toby
--
Tobias McNulty
Data Description, Inc.
840 Hanshaw Road, Suite 9
Ithaca, NY 14850
Phone: (607) 257-1000
E-mail: [EMAIL PROTECTED]
Web: www.datadesk.com
