Oxygen XML Forum

In oxygen 9.x, I could drop a jar file that defined xpath extension functions into
oxygen/lib, and these functions would be recognized both for validation and
debugging.

In oxygen 10.1 (using Saxon B 9.1.0.5), this method is no longer working.
I've also tried defining a transformation scenario and adding the jar to that
scenario. With both methods, I get an error:

SystemID: /Java/apache-tomcat-6.0.18/webapps/vivaxtf/style/textIndexer/common/preFilterCommon.xsl
Severity: fatal
Description: Error in call to extension function {public static boolean org.cdlib.xtf.xslt.FileUtils.exists(net.sf.saxon.expr.XPathContext,java.lang.String)}: Exception in extension function java.lang.NoSuchMethodError: net.sf.saxon.expr.XPathContext.getOrigin()Lnet/sf/saxon/trace/InstructionInfoProvider; - net.sf.saxon.expr.XPathContext.getOrigin()Lnet/sf/saxon/trace/InstructionInfoProvider;
Start location: 46:0

The extensions should be visible once you paste the jar in the lib folder. From the error message however it seems that the extensions do not work with the latest version of Saxon that comes with oXygen 10.1. Please try to re-compile them with Saxon 9.1.0.5 and see if that works.

Best Regards,
George

It does appear to be a saxon issue and not oxygen.
It works from the command line for ver 9.0.0.4J
It does not work from command line for saxonb9-1-0-5j.

I haven't yet found anything in the saxon release note that would explain
why it broke.

Not sure what you mean by compile with 9.1.0.5 .
The extension functions don't reference saxon, so saxon isn't used in
compiling any extensions. From the extensions POV, version of saxon
doesn't matter. Obviously, this isn't the case the other way around.

I haven't yet found anything in the saxon release note that would explain
why it broke.

Oops. I was looking at "Extensions" rather than "Extensibility" section:

http://www.saxonica.com/documentation/c ... ity91.html

It may have something to do with the tightening of the type rules.