BaseX-Talk

basex-talk@mailman.uni-konstanz.de

6 participants
5269 discussions

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

Re: [basex-talk] BaseX 10 • The Double-Digit Summer Edition
by Andy Bunce 03 Aug '22

03 Aug '22

>Makes toggling a comment somewhat challenging. :) Yes, time to dig out that editor key cheat sheet... <home> <shift+end> <ctl+k> On Wed, 3 Aug 2022 at 12:48, Graydon Saunders <graydonish(a)gmail.com> wrote: > I'm seeing the same thing on Linux -- Fedora 36 -- with a trackball. > > 07:45 graydon % java -version > openjdk version "17.0.4" 2022-07-19 > OpenJDK Runtime Environment (Red_Hat-17.0.4.0.8-1.fc36) (build 17.0.4+8) > OpenJDK 64-Bit Server VM (Red_Hat-17.0.4.0.8-1.fc36) (build 17.0.4+8, > mixed mode, sharing) > > I can select individual words by double-clicking them, but no > click-and-drag selection. Makes toggling a comment somewhat challenging. :) > > -- Graydon > > On Wed, Aug 3, 2022 at 7:07 AM Andy Bunce <bunce.andy(a)gmail.com> wrote: > >> Looks good to me. >> I like the renamings and I look forward to taking a look at how the >> locking changes play out >> >> One minor issue I have is: in the GUI editor Mouse-down+ drag is not >> selecting text. This is on Win10 with a trackpad and Java version as below. >> >> /Andy >> >> IMPLEMENTOR="Eclipse Adoptium" >> IMPLEMENTOR_VERSION="Temurin-11.0.15+10" >> JAVA_VERSION="11.0.15" >> JAVA_VERSION_DATE="2022-04-19" >> >> >> On Tue, 2 Aug 2022 at 08:14, Marco Lettere <m.lettere(a)gmail.com> wrote: >> >>> THANKS! >>> >>> M. >>> >>> On 01/08/22 15:27, Christian Grün wrote: >>> > Dear all, >>> > >>> > It’s been around 15 years ago when the first Open-Source version of >>> > BaseX was released. Thanks to the continuous support of all of you, we >>> > are thrilled today to announce the first double-digit version of our >>> > XML framework: >>> > >>> > https://basex.org/ >>> > >>> > BaseX 10 assists you with your everyday data challenges with some >>> > great new features: >>> > >>> > STORAGE >>> > >>> > • Beside XML Documents and Binary Data, you can use the new »XQuery >>> > Values« resource type to store arbitrary items and sequences in >>> > databases. >>> > • General data (registered users, scheduled services, and key-value >>> > stores) can now be backed up as well. >>> > • Mixed-content developers will be delighted: Whitespaces are now >>> > preserved by default. >>> > >>> > XQUERY >>> > >>> > • Database locking has been improved by splitting up XQuery >>> > compilation into a static and dynamic step. >>> > • A new Store Module allows you to organize values in a persistent >>> > main-memory key-value store. >>> > • You can store and retrieve XQuery values with db:put-value and >>> db:get-value. >>> > • When serializing XML, indentation is now turned off by default. >>> > >>> > GENERAL >>> > >>> > • BaseX 10 requires Java 11 to run. >>> > • The GUI comes with improved HiDPI support, new icons and improved >>> consistency. >>> > • All HTTP requests are now based on the new Java HTTP client. >>> > • Catalog support is now universal and based on either the new XML >>> > Catalog API or Norman Walsh’s excellent XML Resolver. >>> > • The default ports for web applications were changed from 8984/8985 >>> > to 8080/8081. >>> > • The default admin password was removed to improve security. >>> > • Results of the REST API are now wrapped in the default REST >>> namespace. >>> > >>> > We have taken the version jump as an opportunity to rename various >>> > existing functions and commands. The database storage has not changed: >>> > Databases created with BaseX 10 are backward compatible and can still >>> > be opened with BaseX 9. >>> > >>> > Visit our documentation for more details, and information on how to >>> > upgrade your existing applications: >>> > >>> > https://docs.basex.org/wiki/BaseX_10 >>> > >>> > Have fun! >>> > Your BaseX Team >>> >>

4 4

Multi-valued values in maps - sequences vs arrays
by Bridger Dyson-Smith 03 Aug '22

03 Aug '22

Hi all - I would appreciate some help understanding how I might go about having a multi-valued array as the value of a map key, or if this is even possible; e.g. map{ "key": [1,2,3,4,5] } I've tried various combinations of array:flatten and array:join, but things always wind up in a sequence. (Aside: this isn't a real problem, but I'm trying to force myself to get more comfortable working with arrays and maps and this seemed like a great exercise... :) My mistake!). E.g. map:merge( (1 to 5) ! map {'key': array:flatten(array { . }) }, map{"duplicates":"combine"} ), (: returns map{"key":(1,2,3,4,5)} :) map:merge( (1 to 5) ! map {'key': array:join(array {.}) }, map{"duplicates":"combine"} ) (: returns map{"key":([1],[2],[3],[4],[5])} :) Are sequences the result because a map is a function item? Thanks for any clarity you can provide! Best, Bridger

3 3

BaseX 10 • The Double-Digit Summer Edition
by Christian Grün 03 Aug '22

03 Aug '22

Dear all, It’s been around 15 years ago when the first Open-Source version of BaseX was released. Thanks to the continuous support of all of you, we are thrilled today to announce the first double-digit version of our XML framework: https://basex.org/ BaseX 10 assists you with your everyday data challenges with some great new features: STORAGE • Beside XML Documents and Binary Data, you can use the new »XQuery Values« resource type to store arbitrary items and sequences in databases. • General data (registered users, scheduled services, and key-value stores) can now be backed up as well. • Mixed-content developers will be delighted: Whitespaces are now preserved by default. XQUERY • Database locking has been improved by splitting up XQuery compilation into a static and dynamic step. • A new Store Module allows you to organize values in a persistent main-memory key-value store. • You can store and retrieve XQuery values with db:put-value and db:get-value. • When serializing XML, indentation is now turned off by default. GENERAL • BaseX 10 requires Java 11 to run. • The GUI comes with improved HiDPI support, new icons and improved consistency. • All HTTP requests are now based on the new Java HTTP client. • Catalog support is now universal and based on either the new XML Catalog API or Norman Walsh’s excellent XML Resolver. • The default ports for web applications were changed from 8984/8985 to 8080/8081. • The default admin password was removed to improve security. • Results of the REST API are now wrapped in the default REST namespace. We have taken the version jump as an opportunity to rename various existing functions and commands. The database storage has not changed: Databases created with BaseX 10 are backward compatible and can still be opened with BaseX 9. Visit our documentation for more details, and information on how to upgrade your existing applications: https://docs.basex.org/wiki/BaseX_10 Have fun! Your BaseX Team

5 5

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

BaseX-Talk