August 2025 - BaseX-Talk - mailman.uni-konstanz.de

Add namespace bindings via copy/modify/return
by Hans-Juergen Rennau 25 Sep '25

25 Sep '25

Dear BaseX people, I cannot use copy/modify/return in order to add a namespacing: let $doc := <doc><a/></doc>return copy $doc_ := $doc modify insert node namespace xyz {'https://basex.org/ns'} into $doc_ return $doc_ =><doc> <a/></doc> Is this a bug? Kind regards,Hans-Jürgen

5 9

array:sort, array:sort-by, and docs access
by Bridger Dyson-Smith 23 Aug '25

23 Aug '25

Dear Christian and BaseX friends, I hope this email finds you well! I had a question about function signatures: it would seem that there's a typo/issue with the signature (and final example) for array:sort[1,2]. Shouldn't the signature for array:sort read: array:sort( $array as array(*), $collation as xs:string? := fn:default-collation(), $key as fn(item()*) as xs:anyAtomicType* := fn:data#1 ) as item()* (cribbed from the qt4cg.org specs[3])? Unless I'm misreading the signature... in which case, excuse me! Additionally, the current signature for array:sort seems to be in approximate alignment with array:sort-by, which is missing from our lovely BaseX docs' array page. To further my confusion, it looks like the examples from the qt4cg.org array:sort-by[4] signature work generally in my BaseX 12.0. Could that be added, or is the function still waiting in the BaseX wings? :) Best wishes, Bridger [1] https://docs.basex.org/main/Array_Functions#array:sort [2] the example `array:sort( [ 1, 2, 3 ], keys := fn($n) { -$n })` throws an error in BaseX 12.0: [XPST0017] array:sort(array[,collation,key]): Unknown keyword: keys. I'll update the example if I may please have access, otherwise, change `keys` to `key`, please. [3] https://qt4cg.org/specifications/xpath-functions-40/Overview.html#func-arra… [4] https://qt4cg.org/specifications/xpath-functions-40/Overview.html#func-arra…

2 2

Tracking xquery:fork-join()
by Johannes Bauer 13 Aug '25

13 Aug '25

Hi, I have question regarding parallel processing of requests. We use the following (simplified) code to run fulltext searches on multiple databases with xquery:fork-join() in parallel. The performance is tracked and logged with prof:time(). declare function documents:search-dbs($dbs as xs:string*, $query as xs:string) as element()* { let $funcs := for $db in $dbs return function() { documents:search-db($db, $query) } return xquery:fork-join($funcs) }; declare function documents:search-db($db as xs:string, $query as xs:string) as element()* { let $data := prof:time( (: Run fulltext search on database here :) (), 'documents:search-db(' || $db || ') ' ) return $data }; The log output looks like this: 17:58:54.125 SERVER admin TRACE documents:search-db(MD) 127.19 ms 17:58:54.139 SERVER admin TRACE documents:search-db(OEM) 142.39 ms 17:58:54.226 SERVER admin TRACE documents:search-db(CS) 229.55 ms 17:58:54.485 SERVER admin TRACE documents:search-db(TEST) 487.16 ms 17:58:54.989 SERVER admin TRACE documents:search-db(ALL) 991.72 ms 17:58:55.205 SERVER admin TRACE documents:search-db(POC) 1206.7 ms 17:58:56.461 SERVER admin TRACE documents:search-db(RO) 2462.38 ms 17:59:00.964 SERVER admin TRACE documents:search-db(US) 6965.86 ms 17:59:01.424 SERVER admin TRACE documents:search-db(PT) 7425.54 ms 17:59:02.260 SERVER admin TRACE documents:search-db(MI) 8262.05 ms 17:59:04.142 SERVER admin TRACE documents:search-db(XP) 10144.15 ms 17:59:05.300 SERVER admin TRACE documents:search-db(AT) 11301.95 ms 17:59:06.353 SERVER admin TRACE documents:search-db(CT) 12356.84 ms 17:59:12.157 SERVER admin TRACE documents:search-db(MR) 18158.48 ms 17:59:14.042 SERVER admin TRACE documents:search-db(LS) 20043.82 ms 17:59:14.999 SERVER admin TRACE documents:search-db(DA) 21000.18 ms To me it seems that the requests are not done in parallel. The request time is always cumulative. Questions: - Is this just an issue of the prof:time() logging? - Do the searches really run in parallel? - Or are they maybe blocked and serialized by some database lock? Any help to analyse this will be appreciated. Best Regards Johannes

1 0

file:current-dir(), file:path-to-native()
by Hans-Juergen Rennau 08 Aug '25

08 Aug '25

Dear BaseX people, I noticed a peculiar behaviour of file:current-dir() on a Windows system. file:current-dir()=>C:\program files\Oxygen XML Editor 25\ file:path-to-native(current-dir()=>C:\Program Files\Oxygen XML Editor 25\ Note the difference: "Program Files" vs. "programfiles". Is this intended? Would one not expect that any path returned by a file:* function *is* native? (Remark: the difference of case can become very important when constructing relative paths.) Kind regards,Hans-Jürgen : On the system in question, the folder "Program Files" is mapped to "programme" (I do not know the reasons. cu

2 2

Migration einer alten RESTXQ-Anwendung nach BaseX 12.0 - ClassNotFoundException für Servlets
by Günter Dunz-Wolff 08 Aug '25

08 Aug '25

"Ich migriere eine bestehende Anwendung von einer alten BaseX-Version auf BaseX 12.0." "Mein systemd-Dienst startet den Server, aber die Anwendung schlägt mit einem 503-Fehler fehl." "Das Log zeigt java.lang.ClassNotFoundException für org.basex.http.rest.RestServlet und org.basex.http.restxq.RestXqServlet." Fügen Sie den Inhalt Ihrer web.xml bei. Frage: "Wie lauten die korrekten Klassennamen und die korrekte web.xml-Konfiguration, um REST und RESTXQ in BaseX 12.0 zu aktivieren?"

2 4

validate:xsd-report - resolving imports
by Hans-Juergen Rennau 08 Aug '25

08 Aug '25

Dear BaseX people, using function 'validate:xsd-report' I notice a surprising behaviour: - if supplying the XSD via URI, it works as expected- if supplying the XSD as node, the imports cannot be resolved Is this a known behaviour and intended? In case it is not, see PS for simple code reproducing the behaviour. Kind regards,Hans-Jürgen PS:(1) doc.xml<doc b:att="99" xmlns:b="http://basex.org"/> (2) schema1.xsd<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:b="http://basex.org" elementFormDefault="qualified"> <xs:import namespace="http://basex.org" schemaLocation="schema2.xsd"/> <xs:element name="doc"> <xs:complexType> <xs:attribute ref="b:att"/> </xs:complexType> </xs:element></xs:schema> (3) schema2.xsd<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" targetNamespace="http://basex.org" elementFormDefault="qualified"> <xs:attribute name="att" type="xs:integer"/></xs:schema> (4) validate.xqvalidate:xsd-report('doc.xml', 'schema1.xsd'),'===',validate:xsd-report('doc.xml', doc('schema1.xsd'))

2 1

Websocket configuration Basex 12
by Andy Bunce 05 Aug '25

05 Aug '25

Hi, I would like to increase the websocket message length from the default of 64 KB. The websocket documentation implies this can be done via web.xml [1] However, while searching for the syntax I came across the suggestion it is different with the Jetty version 12 API [2] The Jetty docs have this example [3] // Configure the ServerContainer. container.setDefaultMaxTextMessageBufferSize(128 * 1024); but my quick code search of the BaseX source found nothing similar. Is it possible to configure the webSocket MaxTextMessageBufferSize in BaseX 12.0? /Andy [1] https://docs.basex.org/main/WebSockets#configuration [2] https://stackoverflow.com/questions/79610426/setting-the-max-buffer-size-fo… [3] https://jetty.org/docs/jetty/12/programming-guide/server/websocket.html#sta…

3 3