I've found the answer for it from this page http://docs.basex.org/wiki/Options
so for the java code in version 8.6.7, it needs to use
System.setProperty("org.basex.dbpath", "/home/xxx/test_basex/");
to set this global path and then, BaseX will read/create collection to this
dbpath correctly.
Hi James,
as to my experience the approach works.
I've tried to use N Slaves BaseX (DB only) instances coordinated by one
Master BaseX including HTTP server. On the latter I implemented a RestXQ
[1] receiving a HTTP request which was then turned into a XQuery and
executed on the different
Hello,
I'm using BaseX version 7.3.1 and I can set dbpath where the collections
are created with this code:
new Set("dbpath", "/home//basex-database").execute(context);
However, when changing to BaseX version 8.6.7, this statement will throw
exception "org.basex.core.BaseXException: Global
Hello Bang,
I am going to assume that you use the quite outdated version 7.3.1 because it
was the only one in the Maven Central repository at the time. Since a few
months we improved the build process and new release are now also available in
Maven Central (but also in the BaseX internal Maven
4 matches
Mail list logo