Bug #4632
closed![Author: Norman Tovey-Walsh](https://www.gravatar.com/avatar/3e18563616902964e16d96a0a43d22c3?rating=PG&size=50&default=https%3A%2F%2Fassets.plan.io%2Fimages%2Fdefault_avatar.png)
![Assignee: Michael Kay](https://www.gravatar.com/avatar/db6526d63053f09b62e52c2da8b2230a?rating=PG&size=22&default=https%3A%2F%2Fassets.plan.io%2Fimages%2Fdefault_avatar.png)
Stylesheet behavior varies depending on presence or absence of an xsl:message
100%
Description
Hi Mike,
I really hope this turns out to be reproducible. I've packaged up a test case that is (currently) reproducible for me, but I'm pretty sure it's come and gone a couple of times while I was chasing it. I'll email the zip to you.
Basically, if you run saxon address.001.xml -xsl:pass/docbook.xsl -o:/dev/null
it succeeds and if you run the same document against fail/docbook.xsl
, it fails. The failure is an attempt to resolve against a URI that isn't absolute (in fact, it's the empty string). Putting in an xsl:message
that prints out the base URI causes it to not be empty.
I'm in the middle of a significant refactoring exercise, so I'm afraid the test case is large and the code is a bit of a mess. As I said, it was very slippery so I just stopped and packaged up the first reproducible case I could catch.
Please register to edit this issue