BaseX-Talk January 2014

basex-talk@mailman.uni-konstanz.de

43 participants
60 discussions

RESTXQ & forward
by Marco Lettere 19 Jan '14

19 Jan '14

Hi all, I'm currently using a pattern where I POST to a rather generic restxq function that performs some pre-validation on the POST body. At that point, according to information I get from the request (path, headers) I call a subsequent more specific function through the <forward/> construct. It works nicely up to the access to the POST content which appears to be consumed defintely by the first function. Actually I get the following error at the called function: [BASX0003] Input could not be converted: "POST.xml" (Line 1): No input found. I don't see in the docs any way I can get forward to pass ahead the bost body and I thought it should be natural ... what am I missing? Regards, Marco Lettere. P.S. I'm using basex 7.7.

3 8

HTTP Module - digest authentication plans?
by Hans-Juergen Rennau 19 Jan '14

19 Jan '14

Dear BaseX team, are there any plans for supporting digest authentication? In my opinion this would be a minor breakthrough for the applicability of BaseX in typical enterprise environments (or at least in mine...), where many services require digest authentication. Support would mean that, for example, very lightweight BaseX scripting can be used for integration tasks and service testing. Another way to put it: highly valuable (and presently via XQuery inaccessible) information would be integrated into the information space on which to operate without further ado - just writing a BaseX script. Hence my strong interest. Kind regards, Hans-Jürgen

4 5

Detect Basex Query Type
by Alireza 17 Jan '14

17 Jan '14

Hi, We would like to detect if a basex query is read query or update query and then only allow read user queries to be executed. We receive a user query from an incoming request like this: http://host:port?query= "xquery" The goal is to check if "xquery" in the url above is a read or update query. We thought about checking the content of the query string and look for update operation keywords such |||||||||||| as insert, delete, etc. Is there any other better way to do that? Best, Alireza

2 1

Limitation on the number of accessed databases
by Fabrice Etanchaud 17 Jan '14

17 Jan '14

Dear all, Is there a limitation on the number of accessed databases via db :xxx functions ? Best regards, Fabrice Etanchaud Questel/Orbit

2 1

Re: [basex-talk] BaseX-Talk Digest, Vol 49, Issue 34
by iClays 17 Jan '14

17 Jan '14

I'm a software engineer who happens to use basex for our content management system. We current use the embedded basex option with Java. There is currently one apache tomcat server to one basex database. Now we are at position of using load balancing where we could have multiple tomcat servers talking to one basex database. Essentially, lets say we have 5 tomcat servers, we will have only one server writing to the only one basex database and the rest of the 4 tomcat servers reading from it. The problem is, after creating the 5 servers and configuring apache httpd server to have a load balancer, we notice a situation in which the first tomcat server opens the basex database and locks it from the rest of the servers access. Any attempt from tomcat server 2 to 4 to open the same database causes exception. How can we resolve this issue? Is there any simple approach to resolving this or BaseX is not designed for this purpose (i.e. one basex database being able to support multiple servers). Also is there a way of making the rest of the tomcat servers have only read access so it doesn't throw exception, etc? Please help.Thanks.

2 1

Variable value nulled when passed to an xsl (smaller DB)
by France Baril 16 Jan '14

16 Jan '14

Hi, I am using BaseX 7.8 beta 3b557bd. When I pass a variable where the value is provided by a function ( *let **$string-variable* := *freeze-test:get-localized-string*('en-us', 'application')) that extracts the data from the database, I cannot pass it as a parameter to an xslt. It nulls the value. I attached a code sample and a simple database that holds a single file. In the sample, if you replace the line : *let **$string-variable* := *freeze-test:get-localized-string*('en-us', 'application') with *let **$string-variable := *'application', you'll notice that the value is output correctly. The issue is not with getting the value. When using the original variable setting (*let **$string-variable* := *freeze-test:get-localized-string*( 'en-us', 'application')), the debug line (*let* *$debug* := *file:write*( 'debug-string-var.txt', *$string-variable*)) does output the extracted value in the .txt file correctly, which means the variable $string-variable has been set, it just doesn't survive being passed as a parameter to xslt:transform. Note that this used to work in BaseX 7.7.2. The fact that the variable gets nulled is a completely new phenomena. To access the test function: http://localhost:8984/test/xsl-params Thanks, France P.S. You can disregard the previous request with larger files (sent to the moderator by the mail server). It looks like old files were still indexed, weighting on the DB size. -- France Baril Architecte documentaire / Documentation architect france.baril(a)architextus.com (514) 572-0341

2 2

Re: [basex-talk] restxq with html form get, syntax to declare variable as argument
by e-letter 16 Jan '14

16 Jan '14

The 'restxq.xqm' was edited as below: (:~ : This module contains some basic examples for RESTXQ annotations : @author BaseX Team :) module namespace page = 'http://basex.org/modules/web-page'; (:~ : This function generates the welcome page. : @return HTML page :) declare %rest:path("{$x}") %output:method("xhtml") %output:omit-xml-declaration("no") %output:doctype-public("-//W3C//DTD XHTML Basic 1.1//EN") %output:doctype-system("http://www.w3.org/TR/xhtml-basic/xhtml-basic11.dtd") function page:start($x) as element(Q{http://www.w3.org/1999/xhtml}html) { <html xmlns="http://www.w3.org/1999/xhtml"> <head> <title>BaseX HTTP Services</title> <link rel="stylesheet" type="text/css" href="static/style.css"/> </head> <body> <h3>Example 2</h3> <p>The next example presents how form data is processed via RESTXQ and the POST method:</p> <form method='get' name='databasequeryform' > <p> <select name='booktitle' > <option> Everyday Italian </option> <option> Harry Potter </option> </select> <input type="submit" value='send' /> </p> </form> </body> </html> }; declare %rest:GET %rest:path("xmldatabasefile.xml/bookstore/book") %rest:form-param("booktitle","{$x}") %rest:produces("text/html") %output:method("xhtml") function page:bookstore() as element(bookstore) { <bookstore> { let $x := fn:doc("xmldatabasefile.xml")/bookstore/book/title[contains(text(),'Everyday Italian')]/parent::* return $x } </bookstore> }; The server response: HTTP ERROR 400 Problem accessing /. Reason: Stopped at /path/to/webapp/restxq.xqm, 58/10: [BASX0003] Variable $x is not specified as argument. Powered by Jetty:// What is my mistake for the declaration: ... function page:bookstore() as element(bookstore) { ...

3 20

Variable value nulled when passed to an xsl
by France Baril 15 Jan '14

15 Jan '14

Hi, I am using BaseX 7.8 beta 3b557bd. When I pass a variable where the value is provided by a function ( *let **$string-variable* := *freeze-test:get-localized-string*('en-us', 'application')) that extracts the data from the database, I cannot pass it as a parameter to an xslt. It nulls the value. I attached a code sample and a simple database that holds a single file. In the sample, if you replace the line : *let **$string-variable* := *freeze-test:get-localized-string*('en-us', 'application') with *let **$string-variable := *'application', you'll notice that the value is output correctly. The issue is not with getting the value. When using the original variable setting (*let **$string-variable* := *freeze-test:get-localized-string*( 'en-us', 'application')), the debug line (*let* *$debug* := *file:write*( 'debug-string-var.txt', *$string-variable*)) does output the extracted value in the .txt file correctly, which means the variable $string-variable has been set, it just doesn't survive being passed as a parameter to xslt:transform. Note that this used to work in BaseX 7.7.2. The fact that the variable gets nulled is a completely new phenomena. To access the test function: http://localhost:8984/test/xsl-params -- France Baril Architecte documentaire / Documentation architect france.baril(a)architextus.com (514) 572-0341

1 0

Experience for management of tons of xml doc using exist-db
by easy 15 Jan '14

15 Jan '14

Hi,all, Based on my discontinuously near ten years experience using exist-db, I made a plan to using exist-db to management more than millions people's EHR, till now, it almost can work, here is what I have done: 1) split the large quantity of doc into small collection( not one collection for one people, but one doc for one people), target to speed query personal info and insert new record nodes. 2) with the kind developer 's help , we can using new range index to quick query big data based on some conditions. 3) using the backup policy to do backup. ... But, there are still some difficult to worry about: 1) exist-db often caused corrupt for a heavy load query, and this often cause db recover fail. and how to avoid heavy load query to affect other query? 2) when will use re-index? after corrupt? the re-index process is very time consumed. how to accelerate re-index? 3) how to control concurrently update db? often this cause the db stop responding to xquery, and as 1). everyday there will more than 1000000 files add to the db, so this is a difficult problem. 4) how to control backup copys ? the backup file will cost large disk space if all old copy exist. Thanks for advice -- 此致 easy 莫愁前路无知己，天下谁人不识君。

2 1

Experience for management of tons of xml doc using exist-db
by easy 14 Jan '14

14 Jan '14

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

BaseX-Talk January 2014