Hi,
importing archives using the GUI containing files with certain characters (e.g. []) leads to exception requesting the base-uri later on. For example importing a archive containing 'files/[Content_Types].xml' file (which is a valid file name) can be imported and results in the mentioned uri which is not valid and will result in an exception using base-uri for nodes contained in the corresponding instance.
Better mask the non allowed chars while importing instead of creating invalid uris.
Alex
Hi Alex,
This reminds me of an older GitHub issue from Eliot Kimber [1].
Maybe it’s something we can tackle with BaseX 10 (a spontaneous solution would introduce conflicts with existing projects and database instances). For now, you can use db:path instead of fn:base-uri.
Hope this helps, Christian
[1] https://github.com/BaseXdb/basex/issues/1172
On Mon, Oct 25, 2021 at 2:39 PM Alexander Witzigmann alexander.witzigmann@tanner.de wrote:
Hi,
importing archives using the GUI containing files with certain characters (e.g. []) leads to exception requesting the base-uri later on. For example importing a archive containing 'files/[Content_Types].xml' file (which is a valid file name) can be imported and results in the mentioned uri which is not valid and will result in an exception using base-uri for nodes contained in the corresponding instance.
Better mask the non allowed chars while importing instead of creating invalid uris.
Alex
basex-talk@mailman.uni-konstanz.de