"Cannot find module class from EXPath repository" error in eXist 3.0

[joewiz]

After installing this in eXist 3.0 (via package manager), adding the required <module> element to conf.xml as directed in the README.md file, and restarting eXist, I get the following error when triggering eXide's function documentation lookup:

<exception>
  <path>/db/apps/eXide/modules/docs.xql</path>
  <message>exerr:ERROR Cannot find module class from EXPath repository: org.exist.xquery.rdf.SparqlModule [at line 46, column 46, source: /db/apps/eXide/modules/docs.xql]
In function:
	local:get-matching-functions(xs:string) [174:13:/db/apps/eXide/modules/docs.xql]</message></exception>

Steps to reproduce:

1. Install this package in eXist 3.0 via Dashboard > Package Manager > Available
2. Add <module> element to conf.xml
3. Restart eXist
4. Open eXide (also, latest via Package Manager)
5. Enter concat and hit ctrl-space to trigger lookup of the module. eXide reports an error; opening Chrome Developer tools > Network shows the request to docs.xql returns a 400 Bad Request error, with the response body showing the error above.

I'd be happy to test fixes.

[wsalesky]

@ljo
I also have this issue on eXist 3.1, running on linux, installing the package from the Package Manager. Note I was able to successfully deploy a version of the code on my Mac OSX environment, by building the package locally and then loading the .xar into the dashboard from my local build. This was unsuccessful for my linux install.

RDF integration is a high priority issue for my project, is there anything I can do to help resolve this issue? I'm happy to test any fixes.

[adamretter]

Should be fixed by #3

[duncdrum]

@adamretter is there a specific reason for semver-min="3.2.0" or should this run on 3.1 or even 3.x?

[adamretter]

@duncdrum Actually that was conservative as I wanted people to test it. Really it relies on the upcoming 3.3.0. It is compiled against 20170627-SNAPSHOT at the moment as it needs the exist-testkit jar which isn't in 3.2.0

[duncdrum]

Thanks for the fixes adam, i ll wait until 3.3 behaves nicely before testing SPARQLing then.

[wsalesky]

Thanks for the fix.

[adamretter]

@joewiz @duncdrum is this one resolved with my PR?