> While the multiple top-level elements of output is not OK for an XML document, > I don't think anything stops you from emitted such with XSL, and my test with > org.apache.xalan.xslt.Process did work. Did it not work for you because of > what > you were doing with the output or the Transform simply refuse to run with > these xslt files?
Actually I’m connecting the transformer to a DOMResult (which makes it easier to compare the output of different XSLT engines). Apparently the problem was that the transformer couldn’t create multiple root nodes inside the DOMResult. > I can't either. One can see how the "/" could be relevant to getting the param > passed down through a hidden root element (if somehow it passed it), but I'm > almost sure I saw the problem come and go with other changes less easy to > rationalize, and your original case of it not working with the key usage but > working without the key usage seem to be a case of that. So I still think > there > is an unexplained "stirring the pot" effect going on, even if you have found a > way to stir the pot to where it works for your purposes. I would worry that > some future code change would stir your pot again and cause things to break > again. Maybe someone from the developers may have an interest in looking into this? > (I am also doing these tests on Unix, and your line breaks indicate Windows, > and > while I think I cleaned that up before my most recent tests, one could imagine > something hidden going on with an editor silently introducing or eliminating > what > xalan counts as additional nodes.) Yes, I am working on Windows. Sergey Bederov Senior Developer Cortona3D www.cortona3D.com<http://www.cortona3d.com/>
