BaseX-Talk

basex-talk@mailman.uni-konstanz.de

3 participants
5267 discussions

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 04 Aug '25

04 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

Re: BaseX version, installation recommendations
by Martin Honnen 23 Jul '25

23 Jul '25

On 23/07/2025 22:49, Rory Campbell-Lange wrote: > On 23/07/25, Martin Honnen via BaseX-Talk (basex-talk(a)mailman.uni-konstanz.de) wrote: >> On 23/07/2025 18:42, Graydon Saunders wrote: >>> The zip package from (currently) >>> https://files.basex.org/releases/12.0/BaseX120.zip >>> unpacks and you're basically done. > ... > >>> On Wed, Jul 23, 2025, at 12:06, Rory Campbell-Lange wrote: >>>> I may be working soon on a commercial server supporting XQuery 3.1+ >>>> with its own proprietary extensions, and XSLT 2.0. >>>> >>>> Would basex 12 be the best match for these protocol versions (except >>>> of the proprietary components, of course)? I'm most interesting in >>>> working in an iterative fashion on the command line, as I'm used to >>>> doing with vim and psql (the postgresql interactive terminal). >> If you want XSLT 2.0 with BaseX, you additionally need to add Saxon HE >> that the currently supported versions 12 and 11 of Saxon are really XSLT 3.0 >> processors, not XSLT 2.0. > Thank you for the clarification about XSLT 3.0, Martin and Graydon. > > I've installed the latest basex (BaseX 12.1) and put Saxon-HE.jar in the lib folder. > > The example from page 116 of "XSLT, 2nd Edition" by Doug Tidwell which has an XSLT 2.0 example with the use of `separator` for <xsl:value-of>. > > Running > > saxon -s:cars.xml -xsl:cars.xsl -o:/tmp/o.xml > > works fine (where "saxon" means `java -jar /usr/share/java/Saxon-HE.jar $@`). > > Whereas: > > basex -o /tmp/o.xml "xslt:transform('cars.xml', 'cars.xsl')" > > Fails with: > > Stopped at <path>/basex/, 1/15: > [FODC0002] "" (Line 1): Content is not allowed in prolog. > > I assume I need to do something to fix the install path of the Saxon-HE.jar file. > > At the risk of trying everyone's patience further, further advice would be helpful. > I am afraid, somewhere along the postings, I messed the location up, I have looked at my BaseX 12 installation and it has a "lib" folder which has a "custom" sub folder in which I have the Saxon HE jar saxon-he-12.8.jar. That "custom" subfolder has another "lib" sub folder in which I have the libraries Saxon depends on, namely xmlresolver-5.3.3.jar, xmlresolver-5.3.3-data.jar and jline-2.14.6.jar (this lib folder with the xml resolver and jline jars is part of the Saxon HE 12 download you find on Github e.g. https://github.com/Saxonica/Saxon-HE/releases/download/SaxonHE-12-8/SaxonHE…). A minimal command line I am able to run (it is Windows Powershell) is e.g. C:\Users\marti\.jdks\temurin-17.0.15\bin\java.exe -cp '.\BaseX.jar;.\lib\custom\saxon-he-12.8.jar' org.basex.BaseX "xslt:transform('sample1.xml', 'sheet1.xsl')" I hope that gets you up and running.

1 0

command line xsl transformation
by Rory Campbell-Lange 23 Jul '25

23 Jul '25

Hi -- beginner here. I've installed basex via apt on Debian. ii basex 10.5-1 all XML database and XPath/XQuery processor I've successfully made and interrogated a database and made a few basic xquery commands from the command line. I'm hoping to use basex for xsl transformations from the command line so that I can work rapidly on iterating towards the transformation I'm trying to achieve. Specifically, I'm aiming to transform an XML document using an XSL document to produce an HTML document. I've tried the following, plus other variants: basex -W -i input.xml -o out.html transform.xsl However the resulting file at out.html is simply the transform.xsl file. I'd be grateful for advice. Many thanks, Rory

6 11

BaseX version, installation recommendations
by Rory Campbell-Lange 23 Jul '25

23 Jul '25

Dear List I may be working soon on a commercial server supporting XQuery 3.1+ with its own proprietary extensions, and XSLT 2.0. Would basex 12 be the best match for these protocol versions (except of the proprietary components, of course)? I'm most interesting in working in an iterative fashion on the command line, as I'm used to doing with vim and psql (the postgresql interactive terminal). If basex 12 is recommended, any pointers to getting this running on Debian would be gratefully received. Unfortunately Debian testing (https://packages.debian.org/sid/basex) still points to basex 10.5. I'm not familiar with Java installation requirements. Thank you for the project, which looks excellent. Many thanks, Rory

3 2

csv:doc(), csv:parse() functions are not respecting the 'field-delimiter': 'tab' parameter
by Yitzhak Khabinsky 21 Jul '25

21 Jul '25

Hello, I am using BaseX 12.0 It seems that the csv:doc(), csv:parse() functions are not respecting the 'field-delimiter': 'tab' parameter. It emits the following error: [csv:parse] The value of 'field-delimiter' is not a single character: 'tab'. Though the old style parameter is working: 'separator': 'tab' It is documented here: https://docs.basex.org/main/CSV_Functions#options Repro is below. Failing XQuery =============== declare variable $csv_file as xs:string external := 'c:\path\to\input.txt'; declare variable $xml_file as xs:string external := 'c:\path\to\output.xml'; let $input_options := { 'header': false(), 'trim-whitespace': true(), 'field-delimiter': 'tab' } let $output_options := {'indent': 'yes', 'method': 'xml', 'encoding': 'UTF-8'} return csv:doc($csv_file, $input_options) -> file:write($xml_file, ., $output_options) Working XQuery =============== declare variable $csv_file as xs:string external := 'c:\path\to\input.txt'; declare variable $xml_file as xs:string external := 'c:\path\to\output.xml'; let $input_options := { 'header': false(), 'trim-whitespace': true(), 'separator': 'tab' } let $output_options := {'indent': 'yes', 'method': 'xml', 'encoding': 'UTF-8'} return csv:doc($csv_file, $input_options) -> file:write($xml_file, ., $output_options) Regards, Yitzhak Khabinsky

2 3

Restore from Backup: Should it work to restore backup from system A on system B?
by Eliot Kimber 09 Jul '25

09 Jul '25

Using BaseX 11.6 on RHEL 9, I created a backup of a database on system A, copied the zip to my personal machine, then used the DBA upload and restore to recreate the database on the new server. I verified that the Zip has the expected data files, so it looks legit. The database is created but no data is loaded, so the database shows 0 bytes. Should this load have worked? I can also just scp the database from one server to the other if that is reliable, or just unzip the zip on the target server—should that work? Cheers, E. _____________________________________________ Eliot Kimber Sr. Staff Content Engineer O: 512 554 9368 servicenow servicenow.com<https://www.servicenow.com> LinkedIn<https://www.linkedin.com/company/servicenow> | X<https://twitter.com/servicenow> | YouTube<https://www.youtube.com/user/servicenowinc> | Instagram<https://www.instagram.com/servicenow>

2 3

Problem (BaseX 12) serializing a map with json:serialize() in combination with the http-client module
by Andreas Hengsbach | nexoma 08 Jul '25

08 Jul '25

Hi everyone, I have found a problem when serializing a map to JSON. I use the following map as request body for the http-client: map { 'username' : "aaa", 'password' : "bbb", 'grant_type' : 'password' } => json:serialize() In 10.4 everything works fine. In 12.0 this now leads to an error when I send the request. (Response from service: <code type="number">400</code><message>Invalid json message received</message>) It seems that the request body is being escaped twice when interacting with the http client. If I omit json:serialize(), it works fine in BaseX 12. I would expect json:serialize() to recognize the map(*) data type and serialize it correctly. Best regards Andreas

5 5

Bug related to copy/modify/return and java binding
by Andreas Hengsbach | nexoma 08 Jul '25

08 Jul '25

Hello everyone, I have probably found a bug that is related to copy/modify/return and the java-binding. Anyway, I couldn't narrow down the problem any further. With the following XQuery-Code I get the result “<A>0</A>” in BaseX 10.4 - as expected. In BaseX 12.0 I get an error message “Cannot invoke ”org.basex.query.func.XQFunction.arity()“ because ‘func’ is null”. (: schnipp :) declare namespace ll = "java:java.util.LinkedList"; declare variable $linkedList := ll:new(); copy $test := <A>{ll:size($linkedList)}</A> modify () return $test (: schnapp :) Full StackTrace: NullPointerException: Cannot invoke "org.basex.query.func.XQFunction.arity()" because "func" is null - [org.basex.query.func.FuncCall.value(FuncCall.java:47), org.basex.query.expr.ParseExpr.iter(ParseExpr.java:49), org.basex.query.up.expr.Transform.value(Transform.java:64), org.basex.query.expr.Pipeline.eval(Pipeline.java:96), org.basex.query.expr.Pipeline.value(Pipeline.java:81), org.basex.query.expr.List.value(List.java:205), org.basex.query.expr.If.value(If.java:159), org.basex.query.expr.List.value(List.java:209), org.basex.query.expr.Pipeline.value(Pipeline.java:82), org.basex.query.expr.gflwor.Let$LetEval.next(Let.java:147), org.basex.query.expr.gflwor.Where$1.next(Where.java:41), org.basex.query.expr.gflwor.GFLWOR$1.next(GFLWOR.java:79), org.basex.query.QueryContext.next(QueryContext.java:395), org.basex.query.expr.List$1.next(List.java:162), org.basex.query.QueryContext.next(QueryContext.java:395), org.basex.query.expr.constr.Constr.add(Constr.java:73), org.basex.query.expr.constr.CElem.item(CElem.java:140), org.basex.query.expr.constr.CElem.item(CElem.java:32), org.basex.query.expr.ParseExpr.value(ParseExpr.java:54), org.basex.query.expr.ParseExpr.iter(ParseExpr.java:49), org.basex.query.expr.IterFilter$1.next(IterFilter.java:36), org.basex.query.QueryContext.next(QueryContext.java:395), org.basex.query.expr.List$1.next(List.java:162), org.basex.query.QueryContext.next(QueryContext.java:395), org.basex.query.expr.constr.Constr.add(Constr.java:73), org.basex.query.expr.constr.CElem.item(CElem.java:140), org.basex.query.expr.constr.CElem.item(CElem.java:32), org.basex.query.expr.ParseExpr.value(ParseExpr.java:54), org.basex.query.expr.ParseExpr.iter(ParseExpr.java:49), org.basex.query.expr.IterFilter.value(IterFilter.java:49), org.basex.query.expr.List.value(List.java:209), org.basex.query.expr.Try.value(Try.java:109), org.basex.query.expr.ParseExpr.iter(ParseExpr.java:49), org.basex.query.scope.MainModule.iter(MainModule.java:53), org.basex.query.QueryContext.lambda$iter$4(QueryContext.java:374), org.basex.query.QueryContext.run(QueryContext.java:770), org.basex.query.QueryContext.iter(QueryContext.java:374), org.basex.query.QueryProcessor.iter(QueryProcessor.java:97) Many thanks and best regards Andreas

2 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

BaseX-Talk