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

Very niche question about BaseX 9.5.1 and java bindings
by Andy Bunce 22 Aug '22

22 Aug '22

Hi, I am trying to write a Java property file using v9.5.1 and no new Java code. The code below runs in 9.7.3. Although it only uses 9.5 features in 9.5.1 it produces the error message props:store·java.io.Writer·String cannot be called with (Writer, String). but https://docs.oracle.com/javase/8/docs/api/java/util/Properties.html#store-j… I assume this is a 9.5.1 java binding bug? Any workaround suggestions or details of what the problem is? /Andy ----------------------------------------------- (:~ Using Basex 9.5.1 and assuming a file "test.properties" in folder containing this module:) import module namespace props = "java:java.util.Properties"; declare variable $source:= file:resolve-path("test.properties",file:base-dir()) !(prof:void(props:load·java.io.Reader(Q{java:java.io.FileReader}new(.))),.) ; props:store·java.io.Writer·String( Q{java:java.io.FileWriter}new($source), "The saucer has landed")

2 2

Basex 10.1, cannot execute query for a particular file name
by ykhabins＠bellsouth.net 19 Aug '22

19 Aug '22

Hello, Congrats on the release of BaseX 10.1 I decided to try XQuery 4.0 functionality right away. So, I typed a new query without saving it on the file system as follows: xquery version "4.0"; (1 to 5) -> {. + .} Executed it, and it is worked. I saved it as a file name: [xquery version 4.0] without square brackets. Extension is 0 And I cannot execute it anymore. Why is that? Just when I saved it as [xquery version 4.xq], I was able to execute it again. Just a peculiarity. Regards, Yitzhak Khabinsky

2 2

Memory footprint for a certain query is much higher usisng BaseX10 compared to 9
by Alexander Witzigmann 16 Aug '22

16 Aug '22

Hi, BaseX 10 has a different behavior in memory footprint for the following situation. To avoid passing around data you can create db using the following create (i did this with BaseX 9) declare variable $input := <root><sheet name="SAP">{for $idx in (1 to 10000) return <row>{for $e in $enames return element {$e} { attribute {"content"} {$idx}}}</row>}</sheet></root>; db:create("test-db",$input,"test.xml") Then using the following query on the created db: declare variable $input := db:open("test-db"); <root>{ for $s in $input//sheet[./@name => contains("SAP")] return <sheet>{$s/@*}{ for $r in $s//row let $no := $r/Objektkurztext/@content return <row>{$r/@*}{($r/*,<partno>{$no}</partno>)}</row> }</sheet> }</root> Using BaseX 9 the used memory for the query is round about 2 GB which is ok. Using BaseX 10 Out-of-Memory exception happens in my case used memory is > 12 GB Any thoughts what the reason is - any additional information required? Alex

2 5

New fails without warning when one file out of 27 is locked
by Patrick Durusau 15 Aug '22

15 Aug '22

Greetings! My mistake but I had one file out of 27 open in an editor when I tried to create a new database across the file set. Got the error message that basex 10.0 could not find (file-name), so I chose ok. Apparently basex failed at that point and did not skip the open file. No database was created. Not a problem because I closed the file and re-ran new but curious if that is the expected behavior? Or should it skip the locked file? Thanks for all the hard work! Patrick -- Patrick Durusau patrick(a)durusau.net Technical Advisory Board, OASIS (TAB) Editor, OpenDocument Format TC (OASIS), Project Editor ISO/IEC 26300 Co-Editor, ISO/IEC 13250-1, 13250-5 (Topic Maps) Another Word For It (blog): http://tm.durusau.net Homepage: http://www.durusau.net Twitter: patrickDurusau

2 2

Convert base64 to XML
by ykhabins＠bellsouth.net 15 Aug '22

15 Aug '22

Hello, I am calling a SOAP Web Service via http:send-request(...) method. It returns back base64 encoded XML. Here is how I am converting it into XML: return html:parse(convert:binary-to-string(xs:base64Binary(http:send-request(...))) ) So, I am using three function/method calls: - xs:base64Binary() - convert:binary-to-string() - html:parse() Is there a more straight forward method to convert base64 encoded string to XML in the BaseX 10.0? Regards, Yitzhak Khabinsky

2 4

List of functions created in xquery:eval-update show unexpected behavior
by Wiemer, Sebastian 15 Aug '22

15 Aug '22

Hi, I ran over an unexpected bahavior of BaseX 9.7.3 Can anyone explain? Note: BaseX 9.7.3 is running with MIXUPDATES=true file1.xq: create to functions in a list and call each function with a list comprehension ---- declare function local:bla(){<bla id=""/> }; declare function local:blubb(){<blubb id=""/> }; (local:bla#0,local:blubb#0)!.() ---- Result: as expected <bla id=""/> <blubb id=""/> file2.xq: same as above, but in an xquery:eval --- xquery:eval( ' declare function local:bla(){<bla id=""/>}; declare function local:blubb(){<blubb id=""/> }; local:bla#0,local:blubb#0 ' )!.() --- Result: as expected <bla id=""/> <blubb id=""/> file3.xq: same as file1, but with a little "twist" --- declare function local:bla(){<bla/> update {insert node attribute id {} into .}}; declare function local:blubb(){<blubb/> update {insert node attribute id {} into .}}; (local:bla#0,local:blubb#0)!.() --- Result: as expected <bla id=""/> <blubb id=""/> file4.xq trying to call the same with xquery:eval will not work ([xquery:update] No updating expression allowed.), so we use xquery:eval-update() --- xquery:eval-update( ' declare function local:bla(){<bla/> update insert node attribute id {} into .}; declare function local:blubb(){<blubb/> update insert node attribute id {} into .}; local:bla#0,local:blubb#0 ' )!.() -- Result: expected <bla id=""/> <blubb id=""/> But the result is: local:bla#0 local:blubb#0 file5.xq: --- xquery:eval-update( ' declare function local:bla(){<bla/> update insert node attribute id {} into .}; declare function local:blubb(){<blubb/> update insert node attribute id {} into .}; local:bla#0 ' )() --- Result: as expected <bla id=""/> Is this a bug? A for-loop will not work either. Best regards, Sebastian IT-Tacheles – IT-Themen auf den Punkt Folge 38: Datenplattformen https://www.adesso.de/de/news/it-tacheles/folge-38.jsp?pk_campaign=ittachel… ------------------------------------------------------- >>> business. people. technology. <<< ------------------------------------------------------- adesso SE mit Sitz in Dortmund Vorstand: Michael Kenfenheuer (Vors.), Dirk Pothen, Andreas Prenneis, Stefan Riedel, Jörg Schroeder, Torsten Wegener Vorsitzender des Aufsichtsrates: Prof. Dr. Volker Gruhn Amtsgericht Dortmund HRB 20663

2 2

Error messages in Basex 9.7.x
by Marc Coenegracht 14 Aug '22

14 Aug '22

Hello Christian, In a clean install of Debian 11, openjdk version "11.0.16" 2022-07-19, I unzipped BaseX973.zip and started the the HTTP server with: basexhttp -S (with debugging set to true). The following error-message appeared: java.lang.IllegalThreadStateException: process hasn't exited at java.base/java.lang.ProcessImpl.exitValue(ProcessImpl.java:521) at org.basex.util.Util.error(Util.java:311) at org.basex.BaseXHTTP.start(BaseXHTTP.java:301) at org.basex.BaseXHTTP.<init>(BaseXHTTP.java:125) at org.basex.BaseXHTTP.main(BaseXHTTP.java:54) which is repeated 10 times (all messages are exactly identical) If the server gets started with: 'basexhttp &' all is fine, no errors. The server starts up normally after these errors and it can be shut down cleanly again. In a few of my scripts the following errors pops up: Creating Database... java.lang.ClassNotFoundException: com.sun.org.apache.xerces.internal.util.XMLCatalogResolver at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:581) at ... etc (multiple classes, long list) Creating Database... .java.lang.NumberFormatException: For input string: "E" at java.base/jdk.internal.math.FloatingDecimal.readJavaFormatString(FloatingDecimal.java:2054) at ... etc repeated twice. The errors are seemingly without consequence, all is functioning fine and the created databases seem OK. Actually the only reason I noticed the errors is because I made the foolish decision to set debugging to true ... :) I tested versions 9.7 and 9.7.3 on multiple Debian 11 boxes with openjdk 11.0.16, and version 9.7 in an older Debian 9 box with openjdk 11.0.6, results are identical. Best, Marc

2 2

BaseX 10.0 as a SOAP client
by ykhabins＠bellsouth.net 12 Aug '22

12 Aug '22

Hello, I need to call SOAP Web Service based on its URL and WSDL. The Web Service is password protected, and returns back XML. WSDL shows all operations, aka methods. Is it possible to make calls to SOAP Web Service from the BaseX 10.0? Regards, Yitzhak Khabinsky

3 8

Log Analysis Tips?
by Eliot Kimber 10 Aug '22

10 Aug '22

We have released version 1.0 of our Project Mirabel server to our internal users. Now we need to know who’s using it, so time for log analysis. I haven’t given any thought yet to what log analysis might mean. So wondering if there are any tips and tricks for analyzing the BaseX logs when using the BaseX HTTP server. Note that we don’t yet have users implemented, so we’re just looking at HTTP requests with different IP addresses. Thanks, E. _____________________________________________ Eliot Kimber Sr Staff Content Engineer O: 512 554 9368 M: 512 554 9368 servicenow.com<https://www.servicenow.com> LinkedIn<https://www.linkedin.com/company/servicenow> | Twitter<https://twitter.com/servicenow> | YouTube<https://www.youtube.com/user/servicenowinc> | Facebook<https://www.facebook.com/servicenow>

3 3

xquery:eval and permissions [updated]
by Marc Balston 08 Aug '22

08 Aug '22

[apologies - there was a typo in my previous message, please refer to this one instead] Hi, I'm running into a permissions error trying to use xquery:eval. I'm on BaseX 9.7.2. This is the error I get when running the query on the server using the REST service (using the default 'reader' user)... [basex:permission] No admin permission: xquery:eval($qString_50, map { "": db:open-pre("Modes", 0)}, map{"permission": "read", ... }) This is the line in the query which throws the error: let $set_combined := xquery:eval($qString, map{'': db:open($db)}, map{'permission': 'read'}) The query string itself, which is passed to eval is a very simple selection, for example: /Interchange/Object[Identification/ObjectName/Keyword/text() = "plate"] Have I misunderstood the purpose of the permission option in xquery:eval? I assumed by setting it to 'read' it would ensure that anyone with read permission would be able to execute it. The query string itself shouldn't require higher permissions in order to be evaluated. Many thanksMarc M. Balston M: +44 7786 263 906 RegardsMarc M. Balston M: +44 7786 263 906

2 4