Thank you very much for the information, Craig. I also suspect that Xalan is the culprit, but had not realized Xalan was bundled with my Java, not with FOP. So I'm glad I asked (and that you answered!)
Having read the FAQ you pointed me to, I spent an hour or so fighting with Xalan and the system to get that working, with some, but not sufficient, success. So I gave up on making this a one-step procedure, installed SaxonB 9.1 (as the java on this system is too old for the current version, SaxonHE 9.2), and now just perform the XML -> FO transformation as a completely separate step before calling FOP. Given that this is being run from a script, it doesn't matter. Thanks again! > It looks like fop is using Xalan for XSLT processing and XPath > support. > I'm guessing (and I do mean guessing) that your issue will come > down to different versions of Xalan, since matches() is added by > xpath 2.0. > Xalan is bundled in 1.4.2-01 and up according to some quick > searching. So I suspect you're using an elderly version of Xalan > from the old JRE/JDK on the sun box that doesn't understand > matches(). You might need to override the bundled version of Xalan. > See: "Q. How do I override the JAXP implementation in JDK 1.4 and > above?" in : http://people.apache.org/~edwingo/jaxp-faq.html --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
