BaseX not picking up the `.basex` configuration file when using XML Calabash
I'm using BaseX 13.0 with XML Calabash 3.0.54, Java 21 on Windows 11.
When I run a XQuery using XML Calabash and BaseX none of the options I specify in a .basex configuration file are used.
I've run the XQuery expression Q{java:org.basex.util.Prop}HOMEDIR() using XML Calabash to see what BaseX thinks the home directory is, and it gives the results I expect.
For my current user directory:
- When I don't have .basex or .basexhome file the XQuery expression returns the directory BaseX is installed in.
- When I create either a .basex or .basexhome file the XQuery expression returns the current user directory, so it recognises it as the home directory.
If I put the following in the .basex file in my current user directory: DEBUG=yes
DUMMY=unknown
the output is no different to not having the .basex file.
Note: setting org.basex.DEBUG=yes as a Java system property displays messages in the terminal window, so I expect the same messages by setting DEBUG=yes in the .basex configuration file.
Note: I expect the DUMMY=unknown to produce some warning/error message.
BaseX obviously knows there is a .basex file there, but doesn't seem to be reading the contents, or acting on the contents.
BaseX 12.4 also does the same.
I can provide details of my XMLCalabash XProc pipeline if required.
Adrian
Quoted text · Adrian Bird · 6 lines
On Sat, 7 Nov 2026 16:16:48 +0000 Adrian Bird via BaseX-Talk <basex-talk at mailman.uni-konstanz.de> wrote: > I'm using BaseX 13.0 with XML Calabash 3.0.54, Java 21 on Windows 11. > > When I run a XQuery using XML Calabash and BaseX none of the options I > specify in a `.basex` configuration file are used.
On a linux shell sometimes i find it helpful to use something like, strace -e openat -f calabash |& fgrep .basex (or, grep -F, it’s the same these days).
If you are on macos i think it’s maybe dtrace instead.
This will show you everwhere the process and any child process (because of -f) tries to open a file containing ".basex", using fgrep so the . is not a regular expression metacharacter that matches any charcter.
Of course, this says where BaseX is looking but not why.
liam
Hi Adrian,
I can only guess what is going on in Calabash. A likely cause could be that the .basex file is simply ignored.
(cc @Norm): if that’s the case, an existing new Context(false) call could be replaced with an invocation of new Context().
@Adrian: Could you reproduce the issue with BaseX exclusively (without Calabash)?
Best, Christian
Quoted text · Adrian Bird · 23 lines
Adrian Bird via BaseX-Talk <basex-talk at mailman.uni-konstanz.de> schrieb am Samstag, 7. November 2026 um 17:18: > I'm using BaseX 13.0 with XML Calabash 3.0.54, Java 21 on Windows 11. > > When I run a XQuery using XML Calabash and BaseX none of the options I specify in a `.basex` configuration file are used. > > I've run the XQuery expression `Q{java:org.basex.util.Prop}HOMEDIR()` using XML Calabash to see what BaseX thinks the home directory is, and it gives the results I expect. > For my current user directory: > - When I don't have `.basex` or `.basexhome` file the XQuery expression returns the directory BaseX is installed in. > - When I create either a `.basex` or `.basexhome` file the XQuery expression returns the current user directory, so it recognises it as the home directory. > If I put the following in the `.basex` file in my current user directory: > DEBUG=yes > DUMMY=unknown > the output is no different to not having the `.basex` file. > Note: setting `org.basex.DEBUG=yes` as a Java system property displays messages in the terminal window, so I expect the same messages by setting `DEBUG=yes` in the `.basex` configuration file. > Note: I expect the `DUMMY=unknown` to produce some warning/error message. > > BaseX obviously knows there is a `.basex` file there, but doesn't seem to be reading the contents, or acting on the contents. > > BaseX 12.4 also does the same. > > I can provide details of my XMLCalabash XProc pipeline if required. > > Adrian
Christian,
Quoted text · Christian Grün · 1 line
> @Adrian: Could you reproduce the issue with BaseX exclusively (without
Calabash)?
No I can't.
Adrian
Quoted text · Norman Walsh · 57 lines
On Sun, 8 Nov 2026 at 19:22, Norman Walsh <ndw at nwalsh.com> wrote: > Very likely my bad. I’ll take a look asap. Probably tomorrow. > > On Sun, 8 Nov 2026, at 18:45, Christian Grün wrote: > > Hi Adrian, > > I can only guess what is going on in Calabash. A likely cause could be > that the .basex file is simply ignored. > > (cc @Norm): if that’s the case, an existing `new Context(false)` call > could be replaced with an invocation of new Context(). > > @Adrian: Could you reproduce the issue with BaseX exclusively (without > Calabash)? > > Best, > Christian > ____________________________________ > > > Adrian Bird via BaseX-Talk <basex-talk at mailman.uni-konstanz.de> schrieb > am Samstag, 7. November 2026 um 17:18: > > I'm using BaseX 13.0 with XML Calabash 3.0.54, Java 21 on Windows 11. > > When I run a XQuery using XML Calabash and BaseX none of the options I > specify in a `.basex` configuration file are used. > > I've run the XQuery expression `Q{java:org.basex.util.Prop}HOMEDIR()` > using XML Calabash to see what BaseX thinks the home directory is, and it > gives the results I expect. > For my current user directory: > - When I don't have `.basex` or `.basexhome` file the XQuery expression > returns the directory BaseX is installed in. > - When I create either a `.basex` or `.basexhome` file the XQuery > expression returns the current user directory, so it recognises it as the > home directory. > If I put the following in the `.basex` file in my current user directory: > DEBUG=yes > DUMMY=unknown > the output is no different to not having the `.basex` file. > Note: setting `org.basex.DEBUG=yes` as a Java system property displays > messages in the terminal window, so I expect the same messages by setting > `DEBUG=yes` in the `.basex` configuration file. > Note: I expect the `DUMMY=unknown` to produce some warning/error message. > > BaseX obviously knows there is a `.basex` file there, but doesn't seem to > be reading the contents, or acting on the contents. > > BaseX 12.4 also does the same. > > I can provide details of my XMLCalabash XProc pipeline if required. > > Adrian > >
Written for BaseX 12.4. BaseX may have changed since: please check the current documentation.