Hi Christian,
thanks for your help.
I didn’t manage to reproduce this; could you please provide us with an SSCCE
Sure:
<commands> <create-db name='test'/> <add path='newdoc'><xyz/></add> <export path='testdb' /> </commands>
When I 1) start the modified basexserver.bat (with last line replaced by java -Duser.dir=C:/tmp -cp "%CP%" %VM% org.basex.BaseXServer %*) and 2) call basexclient -c cmd.xml with the content above, I get an empty testdb folder in basex/bin and a testdb folder containing newdoc in c:\tmp (of course, c:\tmp existed before).
Two more notes: 1) While testing the script, I noticed that my initial description was a bit imprecise: actually, the folder which is created in basex/bin is not named from the database, but from the path='xxx' option given in the export command (i.e. "testdb" for the example above, and not 'test'; unfortunately both were identical in my initial tests).
2) Additionally I found out that the behavior is different when the database is empty: in this case, the folder structure is still created in basex/bin, but *not* in the user.dir path. I do not know what is intended for the export of an empty database - creation of the (empty) export folder structure, or no filesystem operations at all?
Thanks for your help, Greets Simon