I already tried that, and here is the new code:
use strict;
use XML::XSLT;
myy $xslt = XML::XSLT->new ("blog.xsl", warnings => 1, debug => 1);
$xslt->transform ("posts.xml");
print $xslt->toString;
$xslt->dispose();
Alas, same error. I was already making sure that the files did exist and that the variables were being filled, by outputing the vars; I know this isn't a simple file I/O error, in other words.
What I find rather funny is that, when I use the deprecated document_transform function, it kindof works; it prints out only the first template match="/" stylesheet declaration and nothing else.
Furthermore, I know it isn't my XSL or XML files because Xalan works flawlessly. There must be something I'm doing wrong, I just can't find out what, and that error message is not very descriptive (couldn't find anything at byte -1, really? lol) | [reply] [d/l] |
| [reply] [d/l] [select] |
I will prepare these test cases, but I've alread mentioned that these files work flawlessly with Xalan, which is a C-based validating XSLT processor. I assume that XML::XSLT is keeping with the same standard. Also, if it were simply a problem with the xsl/xml, wouldn't you think there would be a more descriptive error, such as: "element illegal" or "element {some element} not found" as opposed to a generic "element not found," as if there was no input at all?
If anyone else has had success with XML::XSLT, please post your code; I'm certain I am just doing something wrong when calling it, but I don't know what. Thanks.
Oh, and here are the links for my current .xsl and .xml files:
XSL
XML
| [reply] |