>(It's not clear to me if it is >assumed there is a single "proper" mapping of Java objects to XSLT >constructs, or if that too is up to the implementation to decide.)
Implementation-specific. I believe Xalan treats these the same way it treats values returned from extension functions (another implementation-specific detail); see the documentation for those. ______________________________________ "... Three things see no end: A loop with exit code done wrong, A semaphore untested, And the change that comes along. ..." -- "Threes" Rev 1.1 - Duane Elms / Leslie Fish (http://www.ovff.org/pegasus/songs/threes-rev-11.html)
