Support #2050: Cannot find a matching 1-argument function named {http://saxon.sf.net/}parse() - Saxon - Saxonica Developer Community

Actions

Send by e-mail Copy link

Support #2050

closed

Cannot find a matching 1-argument function named {http://saxon.sf.net/}parse()

Added by Maksim Selivanov about 10 years ago. Updated over 9 years ago.

Status:

Won't fix

Priority:

Normal

Assignee:

Michael Kay

Category:

Sprint/Milestone:

Start date:

2014-04-14

Due date:

% Done:

Estimated time:

Legacy ID:

Applies to branch:

Fix Committed on Branch:

Fixed in Maintenance Release:

Platforms:

Description

Hi! I have a proper saxon-license.lic and now I downloaded newest Saxon-EE 9.5.1.5 from http://saxonica.com/download/SaxonEE9-5-1-5J.zip, placed saxon9ee.jar, saxon9-sql.jar and saxon9-unpack.jar in build path and got next exception while running Xquery code (worked OK with previous 9.5.1.4):

net.sf.saxon.s9api.SaxonApiException: Cannot find a matching 1-argument function named {http://saxon.sf.net/}parse()

at net.sf.saxon.s9api.XQueryCompiler.compileLibrary(XQueryCompiler.java:476)

at ee.affecto.tis.ehrRules.RuleEngineS9.compileLibrary(RuleEngineS9.java:549)

at ee.affecto.tis.ehrRules.RuleEngineS9.doInitEngine(RuleEngineS9.java:527)

at ee.affecto.tis.CompleteTestSuite.initEngine(CompleteTestSuite.java:241)

at ee.affecto.tis.CompleteTestSuite.setUp(CompleteTestSuite.java:208)

at paring.tlinEhrInteractions.TlinEhrInteractionsSuite.setUp(TlinEhrInteractionsSuite.java:12)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:606)

at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:47)

at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)

at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:44)

at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:24)

at org.springframework.test.context.junit4.statements.RunBeforeTestMethodCallbacks.evaluate(RunBeforeTestMethodCallbacks.java:74)

at org.junit.internal.runners.statements.RunAfters.evaluate(RunAfters.java:27)

at org.springframework.test.context.junit4.statements.RunAfterTestMethodCallbacks.evaluate(RunAfterTestMethodCallbacks.java:83)

at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)

at org.junit.rules.ExpectedException$ExpectedExceptionStatement.evaluate(ExpectedException.java:168)

at org.junit.rules.TestWatcher$1.evaluate(TestWatcher.java:55)

at org.junit.rules.RunRules.evaluate(RunRules.java:20)

at org.springframework.test.context.junit4.statements.SpringRepeat.evaluate(SpringRepeat.java:72)

at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:231)

at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.runChild(SpringJUnit4ClassRunner.java:88)

at org.junit.runners.ParentRunner$3.run(ParentRunner.java:238)

at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:63)

at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:236)

at org.junit.runners.ParentRunner.access$000(ParentRunner.java:53)

at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:229)

at org.springframework.test.context.junit4.statements.RunBeforeTestClassCallbacks.evaluate(RunBeforeTestClassCallbacks.java:61)

at org.springframework.test.context.junit4.statements.RunAfterTestClassCallbacks.evaluate(RunAfterTestClassCallbacks.java:71)

at org.junit.runners.ParentRunner.run(ParentRunner.java:309)

at org.springframework.test.context.junit4.SpringJUnit4ClassRunner.run(SpringJUnit4ClassRunner.java:174)

at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:50)

at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38)

at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467)

at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683)

at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390)

at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:197)

Caused by: net.sf.saxon.trans.XPathException: Cannot find a matching 1-argument function named {http://saxon.sf.net/}parse()

at net.sf.saxon.query.UnboundFunctionLibrary.bindUnboundFunctionReferences(UnboundFunctionLibrary.java:159)

at net.sf.saxon.query.QueryModule.bindUnboundFunctionCalls(QueryModule.java:1096)

at com.saxonica.expr.ee.StaticQueryContextEE.compileLibrary(StaticQueryContextEE.java:73)

at com.saxonica.expr.ee.StaticQueryContextEE.compileLibrary(StaticQueryContextEE.java:142)

at net.sf.saxon.s9api.XQueryCompiler.compileLibrary(XQueryCompiler.java:474)

... 38 more

Actions

Copy link

Updated by Michael Kay about 10 years ago

Status changed from New to In Progress
Assignee set to Michael Kay

I don't think there has been any change between 9.5.1.4 and 9.5.1.5 that should stop saxon:parse() working, and I've just done a quick test that shows it working OK on 9.5.1.5. So I think you must have introduced some configuration problem when upgrading to 9.5.1.5. Perhaps your license key is not valid for this release? Or perhaps it's not being found? Running with the -t option on the command line can help to diagnose such problems.

Actions

Copy link