BaseX-Talk

basex-talk@mailman.uni-konstanz.de

1 participants
5252 discussions

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

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

08 Aug '22

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),'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

1 0

RESTXQ: Handling Lots of Parameters?
by Eliot Kimber 07 Aug '22

07 Aug '22

I’m making a RESTXQ page that handles a form where the form can have a number of different parameters. I’m not seeing a way to define a RESTXQ handler that can handle an arbitrary number of parameters of different names, i.e., if my URL is: https://example.com/form-handler?foo=1&bar=2&fred=3&baz=4 Is there a way to define a RESTXQ handling function that doesn’t have to enumerate each of these parameters in its function declaration? This is mostly looking for a convenience for not having to update a function declaration every time I add a field to a form that is constructed elsewhere and added to the page or maybe a dynamically-constructed form. 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>

2 2

Get All Tokens for Attribute Name?
by Eliot Kimber 07 Aug '22

07 Aug '22

Using the attribute index I can get all attributes of a specific name that have a specific value or token (db:attribute()) and I can get all the values for all attributes that start with a specific prefix (index:attributes()) but I don’t see a way to get, from the index, all the values for all the attributes of a specific name. Have I missed something? My use case is I have an index over my docs where each index entry is of the form: <doc-to-bundle-index-entry key="10503999" filename="c_DataCertification.dita" dbpath="product/data-certification/concept/c_DataCertification.dita" bundles="bundle-platcap-platform-capabilities"/> And I would like the distinct-values of all the @bundles attributes. There are about 40K entry elements. Of course I can do: doc-to-bundle-index/doc-to-bundle-index-entry/@bundles ! tokenize(., '\s+') => distinct-values() And that seems plenty fast, but it seemed like there should be a way to do it with the indexes alone. But it may be that the query on the @bundle attribute actually uses the index anyway… Cheers, 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>

4 5

changes in BaseX-10.0 w.r.t. http:send-request() / fetch:doc() functions?
by Ron Van den Branden 05 Aug '22

05 Aug '22

Hi, After upgrading BaseX to 10.0 (yay!), I notice how http:send-request() calls that used to work in 9.7 are now failing. I didn't find any changes documented between version 9.7 and 10.0 at https://docs.basex.org/wiki/HTTP_Client_Module. Yet (tested with the same JDK), I'm observing differences between BaseX-9.7 and BaseX-10.0. Test case: let $uri := 'http://vocab.getty.edu/aat/300027473.rdf' returnhttp:send-request(<http:request method="get" status-only="true" href="{$uri}"/>) Result: * BaseX-9.7: valid response <http:response xmlns:http="http://expath.org/ns/http-client" status="200" message="OK"> <http:header name="Server" value="Apache-Coyote/1.1"/> <http:header name="Content-Disposition" value="attachment; filename="aat_300027473.rdf""/> <http:header name="Set-Cookie" value="BIGipServerForest=!VhOKP5OjryEOuPhyk3Vb4l5ey77Ecb9C7h36RwDl7h0P+12yggqrxtSz6mEpwv8Du1qdIeJTRfFkqw==; path=/; Httponly"/> <http:header name="Content-Length" value="55888"/> <http:header name="Date" value="Thu, 04 Aug 2022 14:32:02 GMT"/> <http:header name="Content-Type" value="application/rdf+xml;charset=UTF-8"/> <http:body media-type="application/rdf+xml"/> </http:response> * BaseX-10.0: "Bad Request" error <http:response xmlns:http="http://expath.org/ns/http-client" status="400" message="Bad Request"> <http:header name="connection" value="close"/> <http:header name="content-length" value="968"/> <http:header name="content-type" value="text/html;charset=utf-8"/> <http:header name="date" value="Thu, 04 Aug 2022 14:31:56 GMT"/> <http:header name="server" value="Apache-Coyote/1.1"/> <http:header name="set-cookie" value="BIGipServerForest=!mBtphfxjdsqnz+Vyk3Vb4l5ey77EcVUpOTC6kqayu7tj3BpCNxN68oQTs+W4wrEO4+vQ2pECmIF6rA==; path=/; Httponly"/> <http:body media-type="text/html"/> </http:response> The same results are obtained with fetch:xml() (BaseX-9.7 - valid response) and fetch:doc() (BaseX-10.0 - bad request). Apologies if I'm overlooking the obvious, but has anything changed w.r.t. these http / fetch module functions or their underlying methods of network access that would require changes in my XQuery code or BaseX-10.0 configuration? Best, Ron

3 8

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

BaseX-Talk