Well, I'm not sure that Saxon isn't doing the right thing. According to the javadoc for DOMSource: "The operation will be applied to the subtree rooted at this node. In XSLT, a "/" pattern still means the root of the tree (not the subtree), and the evaluation of global variables and parameters is done from the root node also."
As the identity transformation matches "/", this implies that Saxon has implemented the API correctly and perhaps Xalan has implemented it more intuitively. I think it would be safer if we changed the way that the configuration element was extracted and passed in to Jetty. Ie we need to do a deep clone of the configuration Node, then convert that to a string via the transformer and pass that in to Jetty. This will ensure that the xml is rooted at the configuration element. I will look into this further this weekend. cheers, Jan ------------------- Jan Bartel Principal Consultant Mort Bay Consulting UK and Australia ------------------------------------------------------- This sf.net email is sponsored by: With Great Power, Comes Great Responsibility Learn to use your power at OSDN's High Performance Computing Channel http://hpc.devchannel.org/ _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
