You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The versioning.xqm module is missing from target/xquery-versioning-module-1.1.2-exist.jar, when you built the project from the sources.
What did you expect
I expect to have the versioning.xqm in the built target/xquery-versioning-module-1.1.2-exist.jar, in order to use it in eXist.
Describe how to reproduce or add a test
Compile the project as explained here (with the Java 8 and Maven 3 requirement).
Copy the built target/xquery-versioning-module-1.1.2-exist.jar into $EXIST_HOME/lib/user.
In $EXIST_HOME/conf.xml, add the following line in the <builtin-modules> element as explained here: <module uri="http://exist-db.org/xquery/versioning" class="org.exist.versioning.xquery.VersioningModule"/>.
Add also the utility API module: <module uri="http://exist-db.org/versioning" src="resource:org/exist/versioning/xquery/versioning.xqm"/> (paragraph Direct Installation into eXist-db (.jar)). Note: In previous eXist 2.2, the module was located at this path). I think the README miss some explanations about how to cleanly add this module configuration into eXist-db, paragraph Direct Installation into eXist-db (.jar).
Restart eXist-db.
Try to use any functions of the utility API module (example: v:revisions) and see that the module is not found:
Cannot compile xquery: err:XQST0059 error found while loading module v: Source for module 'http://exist-db.org/versioning' not found module location hint URI 'resource:org/exist/versioning/xquery/versioning.xqm'.
Context information
eXist-db version + Git Revision hash: eXist-db 3.1 / c679cd8
xquery-versioning-module version + Git Revision hash: 1.1.2 / 1c1bfba
Java version: Java8u121
Operating system: Windows 7
64 bit
Custom changes: in conf.xml, I added the following line in the <builtin-modules> element as explained here: <module uri="http://exist-db.org/xquery/versioning" class="org.exist.versioning.xquery.VersioningModule"/>
I also added the utility API module: <module uri="http://exist-db.org/versioning" src="resource:org/exist/versioning/xquery/versioning.xqm"/>
I also enabled the serialized filter as explained here.
The text was updated successfully, but these errors were encountered:
What is the problem
The
versioning.xqm
module is missing fromtarget/xquery-versioning-module-1.1.2-exist.jar
, when you built the project from the sources.What did you expect
I expect to have the
versioning.xqm
in the builttarget/xquery-versioning-module-1.1.2-exist.jar
, in order to use it in eXist.Describe how to reproduce or add a test
Compile the project as explained here (with the Java 8 and Maven 3 requirement).
Copy the built
target/xquery-versioning-module-1.1.2-exist.jar
into$EXIST_HOME/lib/user
.In
$EXIST_HOME/conf.xml
, add the following line in the<builtin-modules>
element as explained here:<module uri="http://exist-db.org/xquery/versioning" class="org.exist.versioning.xquery.VersioningModule"/>
.Add also the utility API module:
<module uri="http://exist-db.org/versioning" src="resource:org/exist/versioning/xquery/versioning.xqm"/>
(paragraph Direct Installation into eXist-db (.jar)).Note: In previous eXist 2.2, the module was located at this path). I think the
README
miss some explanations about how to cleanly add this module configuration into eXist-db, paragraph Direct Installation into eXist-db (.jar).Restart eXist-db.
Try to use any functions of the utility API module (example:
v:revisions
) and see that the module is not found:Context information
c679cd8
conf.xml
, I added the following line in the<builtin-modules>
element as explained here:<module uri="http://exist-db.org/xquery/versioning" class="org.exist.versioning.xquery.VersioningModule"/>
I also added the utility API module:
<module uri="http://exist-db.org/versioning" src="resource:org/exist/versioning/xquery/versioning.xqm"/>
I also enabled the serialized filter as explained here.
The text was updated successfully, but these errors were encountered: