You should also be concerned about the possiblity of out-of-order
evaluation, unless your extension code is completely taking over evaluation
of that subtree. Xalan doesn't _currently_ reorder stylesheets, as far as I
know, but part of the reason XSLT was designed as a functional language was
to allow doing so. and you may want to design your extensions with that in
mind.
The strongest promise of sequentiality we've got is that variables will be
assigned before they are referenced. Which, if you're working with
extension functions, may be an answer to your question: You should be able
to take advantage of Xalan's ability to hold non-XSLT values in its
variables and use that to explicitly pass context information from
extension to extension. That also avoids any multitasking issues since each
executing stylesheet has its own variable stack. I grant that it's a bit
ugly, though.
If you're willing to risk reordering... I *think* the SQL Extension has
dealt with the threadsafety issue, but I don't remember how offhand. Might
be worth checking that code.
______________________________________
Joe Kesselman, IBM Next-Generation Web Technologies: XML, XSL and more.
"The world changed profoundly and unpredictably the day Tim Berners Lee
got bitten by a radioactive spider." -- Rafe Culpin, in r.m.filk
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
