BaseX-Talk January 2025

basex-talk@mailman.uni-konstanz.de

11 participants
35 discussions

Problem with default namespace
by Jörn Willhöft 13 Jan '25

13 Jan '25

Hi all, I just come across an issue, and I am not sure if I am too stupid to see the mistake, or it is a bug in BaseX. I need to create an XML document from data in BaseX 11.5 inside basexgui. The data in the database does not use any namespaces. The document I am creating must have a default namespace set. Here is a stripped down example of my XQuery: for $w in /json/workouts/_/header[uuid='123'] return <gpx xmlns="http://www.topografix.com/GPX/1/1" > <title>{$w/title/text()}</title> </gpx> Strangely all XPaths inside and outside the gpx-element will not match anything as long as I have the default namespace on the gpx-element defined. It works if I drop the xmlns attribute or I define the namespace explicitly, like: for $w in /json/workouts/_/header[uuid='123'] return <g:gpx xmlns:g="http://www.topografix.com/GPX/1/1" > <g:title>{$w/title/text()}</g:title> </g:gpx> Even though this should be semantically equal to the output of the above, the third party app that I import this to does not recognize it as such. This is puzzling me mainly because I do not see, why the namespace I define for the *output* xml should have an impact on the queries that are directed to my database. As a workaround I will probably use a regex to remove the namespace, but that's obviously pretty awkward. Any ideas? Cheers Jörn

4 4

Re: [basex-talk] BaseX mail archive stopped working
by Christian Grün 13 Jan '25

13 Jan '25

Hi Yitzhak (cc to the list), Thanks for letting us know. I don’t know who maintains the mail archive. What I know is that the administrators of our mailing list (located at University of Konstanz) will upgrade to a new version of Mailman. Maybe that caused the archiver to stop. If we are lucky, it will work again once the upgrade is completed. Until then, you may need to resort to the threaded list of messages (without search function): https://mailman.uni-konstanz.de/pipermail/basex-talk/ Maybe it’s time for us to write our own little indexer. Or maybe someone else wants to tackle that, as a little XQuery Full Text project? ;) Best, Christian On Mon, Jan 13, 2025 at 3:17 PM <ykhabins(a)bellsouth.net> wrote: > Mr. Grun, > > > > It seems that the BaseX mail archive stopped working starting from > 2025-01-03: > > > https://www.mail-archive.com/basex-talk@mailman.uni-konstanz.de/maillist.ht… > > > > Re: [basex-talk] Basex stops with error: 'Index -1 out of bounds for > length 32'. > <https://www.mail-archive.com/basex-talk@mailman.uni-konstanz.de/msg16014.ht…> > was the last thread. > > > > I received few email notifications dated after 2025-01-03. > > So, it is a proof that the BaseX mail archive is not updated. ☹ > > > > > > *Regards,Yitzhak Khabinsky**Skype: ykhabins* > > >

1 0

Error when passing a value via %rest:form-param in combination with a security function
by Jan Meijer 09 Jan '25

09 Jan '25

In BaseX v11.6 an error occurs when passing a value via "%rest:form-param" in combination with a security function. The example below consists of two RESTXQ functions "p:post" and "p:form". After submitting the form with a value for input "resource-id" the following error occurs in function "p:post": Stopped at /usr/local/basex/webapp/ui/problem.xqm, 16/10: [basex:restxq] Value of "resource-id" must be xs:string, supplied: (). Example module problem.xqm: module namespace p = 'problem'; declare %perm:check('/p', '{$perm}') function p:check( $perm as map(*) ) as element(rest:response)? { }; declare %rest:path('/p/post') %rest:POST %rest:form-param("resource-id", "{$resource-id}") %output:method('html') %output:version('5.0') function p:post( $resource-id as xs:string ) { <div> <p>$resource-id={$resource-id}</p> </div> }; declare %rest:path('/p/form') %rest:GET %output:method('html') %output:version('5.0') function p:form() { <div> <form method="post" action="/p/post"> <input type="text" name="resource-id" id="resource-id" required="required"/><br/> <button type="submit">Ok</button> </form> </div> }; The described behavior is caused by the security function "p:check". 1. If you remove the security function "p:check" it works fine. 2. If you replace `%rest:form-param` with `%rest:query-param` it also works fine, but that doesn't seem right to me. Is this a bug or do I something wrong? Kind regards, Jan Meijer

2 1

Basex stops with error: 'Index -1 out of bounds for length 32'.
by Rob Stapper 03 Jan '25

03 Jan '25

Hi Christian, First of all best wishes for the next year, may it be an interesting one. Having said that, I encountered this 'interesting' issue. I vagely think to remember something lijke this is adressed before but I'm not sure. I hereby send you a self containing application: 'nastyIssueTest2.xq', that triggers the error. I've made the code as small as possible, but since the occurrence of the error very much depends on the context, some context code is necessary. ( I don't think the context code triggers the error but more suppresses it, adding a trace somewhere could make the error just disappear) I suspect that the first function in the app: 'local:for-each-component#4', is the culprit, but I can't really tell. I've also added a workaround in the app: 'local:for-each-component2#2', which seems a stable solution. The issue looks like something like 'https://github.com/BaseXdb/basex/issues/909' of march 2014. Btw. I used version 11.3. Updating to version 11.6 triggers a different error when code of function: 'local:folderDialog.new#2', is activated. When deactivated it triggers the above mentioned error. I hope this helps. mvgr. Rob Stapper

2 1

No create permission error in BaseX fiddle on HTTP(S) request
by Martin Honnen 03 Jan '25

03 Jan '25

Hi folks, today when trying HTTP(S) requests in the BaseX fiddle like e.g. json-doc('https://martin-honnen.github.io/xslt/2024/sample1.json') I get an error No create permission: json-doc("https://martin-honnen.github.io/xslt/2024/sample1.json") Is that some intended restriction/limitation of the fiddle or some bug/quirk that has slipped in?

2 1

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

BaseX-Talk January 2025