BaseX-Talk March 2015

basex-talk@mailman.uni-konstanz.de

36 participants
58 discussions

Facing Problem with Sum()
by ankit kumar 12 Mar '15

12 Mar '15

Hi, I am trying to evaluate this expression, it is supposed to give TRUE but, it is giving false. sum((<a>5923.17</a>,<a>5956.29</a>,<a>5989.28</a>)) = <a>17868.74</a> But, for this expression it is giving as expected. sum((<a>5922.78</a>,<a>-5955.78</a>,<a>5988.74</a>)) = <a>5955.74</a> Thanks Ankit

3 2

Re: [basex-talk] Deploy Base801.war on Jboss EAP 6.1 throws error
by Christian Grün 12 Mar '15

12 Mar '15

Hi Erol (cc to the list), I have added a new option, which now allows you to specify absolute paths for your XQuery modules and command scripts [1]. Hope this helps, Christian [1] http://docs.basex.org/wiki/Options#RESTPATH On Thu, Mar 12, 2015 at 2:01 PM, Christian Grün <christian.gruen(a)gmail.com> wrote: > Hi Erol, > > Sounds reasonable, we could possibly add a new RESTPATH option. I'll > think about it a bit more. > >> Basex documentation says we can configure WEBPATH >> location but I could not. > > Which page in the article do you refer to? It's true, the option is > only considered if BaseX is not started as web servlet. In this case, > your web server decided what will be the web directory. If you are > interested in helping us to improve our Wiki, I welcome you to get an > account! > > Christian > > >> On Mon, Mar 9, 2015 at 9:14 AM, Erol Akarsu <eakarsu(a)gmail.com> wrote: >>> >>> Hi, >>> >>> I deployed Base801.war on Jboss EAP 6.1 with JDK 7. I >>> >>> Jboss can not start web service because of this error: >>> >>> Encountered invalid class name >>> 'org.xmlpull.mxp1.MXParser,org.xmlpull.mxp1_serializer.MXSerializer' for >>> service type 'org.xmlpull.v1.XmlPullParserFactory' >>> >>> Error starting context /BaseX801: java.lang.IllegalArgumentException: >>> JBWEB000250: Child container with name default already exists >>> >>> Do you have any idea on how to fix it? >>> >>> >>> 09:05:22,956 INFO [org.jboss.as.server.deployment] (MSC service thread >>> 1-8) JBAS015876: Starting deployment of "BaseX801.war" (runtime-name: >>> "BaseX801.war") >>> >>> 09:05:23,326 WARN [org.jboss.as.server.deployment] (MSC service thread >>> 1-8) JBAS015893: Encountered invalid class name >>> 'org.xmlpull.mxp1.MXParser,org.xmlpull.mxp1_serializer.MXSerializer' for >>> service type 'org.xmlpull.v1.XmlPullParserFactory' >>> >>> 09:05:23,445 INFO [org.jboss.web] (ServerService Thread Pool -- 88) >>> JBAS018210: Register web context: /BaseX801 >>> >>> 09:05:23,448 ERROR [org.apache.catalina.core] (ServerService Thread Pool >>> -- 88) JBWEB001097: Error starting context /BaseX801: >>> java.lang.IllegalArgumentException: JBWEB000250: Child container with name >>> default already exists >>> >>> at >>> org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:794) >>> [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] >>> >>> at >>> org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:785) >>> [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] >>> >>> at >>> org.apache.catalina.core.StandardContext.addChild(StandardContext.java:1862) >>> [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] >>> >>> at >>> org.jboss.as.web.deployment.JBossContextConfig.processWebMetaData(JBossContextConfig.java:471) >>> [jboss-as-web-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10] >>> >>> at >>> org.jboss.as.web.deployment.JBossContextConfig.applicationWebConfig(JBossContextConfig.java:201) >>> [jboss-as-web-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10] >>> >>> at >>> org.apache.catalina.startup.ContextConfig.start(ContextConfig.java:354) >>> [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] >>> >>> at >>> org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:153) >>> [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] >>> >>> at >>> org.jboss.as.web.deployment.JBossContextConfig.lifecycleEvent(JBossContextConfig.java:194) >>> [jboss-as-web-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10] >>> >>> at >>> org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:115) >>> [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] >>> >>> at >>> org.apache.catalina.core.StandardContext.start(StandardContext.java:3717) >>> [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] >>> >>> at >>> org.jboss.as.web.deployment.WebDeploymentService.doStart(WebDeploymentService.java:156) >>> [jboss-as-web-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10] >>> >>> at >>> org.jboss.as.web.deployment.WebDeploymentService.access$000(WebDeploymentService.java:60) >>> [jboss-as-web-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10] >>> >>> at >>> org.jboss.as.web.deployment.WebDeploymentService$1.run(WebDeploymentService.java:93) >>> [jboss-as-web-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10] >>> >>> at >>> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) >>> [rt.jar:1.7.0_67] >>> >>> at >>> java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_67] >>> >>> at >>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) >>> [rt.jar:1.7.0_67] >>> >>> at >>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) >>> [rt.jar:1.7.0_67] >>> >>> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_67] >>> >>> at org.jboss.threads.JBossThread.run(JBossThread.java:122) >>> >>> >>> >>> 09:05:23,469 ERROR [org.apache.catalina.core] (ServerService Thread Pool >>> -- 88) JBWEB001103: Error detected during context /BaseX801 start, will stop >>> it >>> >>> 09:05:23,470 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool >>> -- 88) MSC000001: Failed to start service >>> jboss.web.deployment.default-host./BaseX801: >>> org.jboss.msc.service.StartException in service >>> jboss.web.deployment.default-host./BaseX801: >>> org.jboss.msc.service.StartException in anonymous service: JBAS018040: >>> Failed to start context >>> >>> at >>> org.jboss.as.web.deployment.WebDeploymentService$1.run(WebDeploymentService.java:96) >>> >>> at >>> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) >>> [rt.jar:1.7.0_67] >>> >>> at >>> java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_67] >>> >>> at >>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) >>> [rt.jar:1.7.0_67] >>> >>> at >>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) >>> [rt.jar:1.7.0_67] >>> >>> at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_67] >>> >>> at org.jboss.threads.JBossThread.run(JBossThread.java:122) >>> >>> Caused by: org.jboss.msc.service.StartException in anonymous service: >>> JBAS018040: Failed to start context >>> >>> at >>> org.jboss.as.web.deployment.WebDeploymentService.doStart(WebDeploymentService.java:161) >>> >>> at >>> org.jboss.as.web.deployment.WebDeploymentService.access$000(WebDeploymentService.java:60) >>> >>> at >>> org.jboss.as.web.deployment.WebDeploymentService$1.run(WebDeploymentService.java:93) >>> >>> ... 6 more >>> >>> >>> >>> 09:05:23,685 ERROR [org.jboss.as.server] (DeploymentScanner-threads - 2) >>> JBAS015870: Deploy of deployment "BaseX801.war" was rolled back with the >>> following failure message: >>> >>> {"JBAS014671: Failed services" => >>> {"jboss.web.deployment.default-host./BaseX801" => >>> "org.jboss.msc.service.StartException in service >>> jboss.web.deployment.default-host./BaseX801: >>> org.jboss.msc.service.StartException in anonymous service: JBAS018040: >>> Failed to start context >>> >>> Caused by: org.jboss.msc.service.StartException in anonymous service: >>> JBAS018040: Failed to start context"}} >>> >>> 09:05:23,766 INFO [org.jboss.as.server.deployment] (MSC service thread >>> 1-3) JBAS015877: Stopped deployment BaseX801.war (runtime-name: >>> BaseX801.war) in 80ms >>> >>> >>

1 0

xml serialisation
by Menashè Eliezer 12 Mar '15

12 Mar '15

Hello, I need xquery reply which is composed of multiple values. I've chosen the xml format, but I need also the collection name of each record since I'm searching in multiple collections. However for parsing the entire reply as xml I need to add an arbitrary xml tag to base-uri($x). I couldn't find a way to do it. Any ideas? Background: I've tried first the JSON format as output:method, however it cannot be used for more than one record. I've tried text format, but I need an attribute and I get: @codeListValue cannot be serialised So, xml format provides me the option to query the attribute, even though the reply length is bigger. I'm using BaseX 8 beta. -- With kind regards, Menashè

3 3

BaseX in JMeter
by Hans-Juergen Rennau 12 Mar '15

12 Mar '15

Hello everybody, has anybody smuggled BaseX into JMeter, for example creating a JMeter plugin using BaseX? The problem: I would like to transform service responses from JSON to XML in order to apply XPath extractions and assertions. Using BaseX, the transformation could be easily accomplished using json:parse + a little post processing which restores the precise XML representation needed. I suppose that a JMeter plugin might be created which executes the query, but I feel unsure if it is a feasible approach. So should anybody have done something similar - managed to bring BaseX into play in the context of JMeter - it would be kind to share the experience. Cheers,Hans-Jürgen

1 0

RESTXQ
by Erol Akarsu 12 Mar '15

12 Mar '15

I need an urgent help here. I am trying to configure restxqpath web.xml like below and compile war file of basex with command mvn compile war:war <context-param> <param-name>org.basex.restxqpath</param-name> <param-value>/home/eakarsu/BasexXQ</param-value> </context-param> I moved dba folder and restxq.xqm to /home/eakarsu/BasexXQ I deployed war file into local tomcat server and accessed http://localhost:8080/BaseX801 It brings the content of file restxq.xqm. But when I call existing restxq services embedded in this file http://localhost:8080/hello/World http://localhost:8080/hello/Universe I am getting 404 error like this HTTP Status 404 - /hello/World Am I missing something? I appreciate your help Erol Akarsu

2 1

Error?
by Lars Johnsen 12 Mar '15

12 Mar '15

Hi all I have a database collection which gives a strange error message '[FODC0002] "" (Line 1): Content is not allowed in prolog.' on this query: for $x in collection('samtiden') return doc(document-uri($x)) The results from document-uri($x) are as expected, but doc(document-uri($x)) should return $x - so what can be the cause of the error? The collection was entered in the gui using "skip corrupt files" since some of the files had errors (ended prematurely). But the database and document-uri() works fine for all elements in the database. I need to process the paths for grouping the documents in the collection, so the practical value is a bit more than just trying to compute a unity function! Best, Lars G Johnsen National Library of Norway

2 5

Database Path preference doesn't persist across sessions (v8.0.1/v8.0.2)
by Amanda Galtman 11 Mar '15

11 Mar '15

Hi, I just started using version 8.0.1 and 8.0.2 after having used version 7.9 for awhile. In some GUI sessions, when I enter a Database Path preference value in the Preferences dialog, the value gets used during that session but does not persist in the next session. The .basex file in my .basexhome directory is not being updated to reflect the value I entered in the dialog. The strange thing is that this might not be the case for every session. My .basex file for version 8.0.1 had a custom value in it, which I know I did not set manually in the .basex file. However, today I cannot get it to reflect any other values that I enter in the GUI. As a workaround, I can manually enter a path on the DBPATH line in my .basex file. But I wanted to report this issue anyway. I am using Windows 7, and the .basex and .basexhome files are in my BaseX installation directory. I would be suspicious about Windows administrator permissions, except that this works fine in BaseX 7.9, where .basex is in an analogous location on my hard drive. Thanks, Amanda

2 2

Re: [basex-talk] CLI issue with 8.0.1
by Olivier Jeulin 10 Mar '15

10 Mar '15

Hi, Doh! Mea culpa: I made an error in the name of the parameter (not the one in the example above), so of course the binding never worked. All of the syntax works (in GNU/linux's bash ), except -b"$db-name=Value" because the shell will interpret $dp, so one must use instead: -b'$db-name=Value' 2015-03-05 10:54 GMT+01:00 Olivier Jeulin <olivier.jeulin.work(a)gmail.com>: > Hello, > > I'm also strugling to pass parameters: > in my XQuery : > declare variable $db-name external; > I tried, following the documentation “-b$v=example” : > basexclient script.xq -b\$db-name=Value > basexclient script.xq -b"$db-name=FichiersBase" > basexclient script.xq -bdb-name=Value > basexclient script.xq -b"db-name=Value" > > and everytime: > [XPDY0002] No value assigned to $db-name. > > What's the correct syntax???! > > > 2015-02-23 16:44 GMT+01:00 Marco Lettere <marco.lettere(a)dedalus.eu>: > >> Hello all, >> I'm unable to execute the example from documentation: >> >> bin/basex -b$v=example "declare variable $v external; $v" >> >> IT gives this exception: >> >> Stopped at ., 1/19: >> [XPST0003] Expecting '$', found 'e'. >> >> Any clues? >> Regards, >> MArco. >> > >

1 0

Concurrent handling of reads while ADDing a file
by David Mathei 10 Mar '15

10 Mar '15

Hello BaseX Team, I am loading a big file into BaseX (2.1G) and try to understand the handling of concurrent reads during that process. The size does only matter in so far, as loading seems to block reading for an extended amount of time. I observe that I can not read the collection I'm loading into nor any other collection under the same server. When I use another server process on a different port to write to the target collection I can read other collections without delay, the collection I'm loading into is (obviously) blocked by the upd.basex flag. Is there no parallelisation involved that would separate reading from writing processes, or does that only come into play for xquery updates that run under the transaction module? My PARALLEL setting is at the default of 8 and I'm on version 8.0.1. And I apologise already if I missed some obvious configuration... Thanks to everyone involved in this project! David Mathei

3 6

Deploy Base801.war on Jboss EAP 6.1 throws error
by Erol Akarsu 09 Mar '15

09 Mar '15

Hi, I deployed Base801.war on Jboss EAP 6.1 with JDK 7. I Jboss can not start web service because of this error: Encountered invalid class name 'org.xmlpull.mxp1.MXParser, org.xmlpull.mxp1_serializer.MXSerializer' for service type 'org.xmlpull.v1. XmlPullParserFactory' Error starting context /BaseX801: java.lang.IllegalArgumentException: JBWEB000250: Child container with name default already exists Do you have any idea on how to fix it? 09:05:22,956 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015876: Starting deployment of "BaseX801.war" (runtime-name: "BaseX801.war") 09:05:23,326 WARN [org.jboss.as.server.deployment] (MSC service thread 1-8) JBAS015893: Encountered invalid class name 'org.xmlpull.mxp1.MXParser,org.xmlpull.mxp1_serializer.MXSerializer' for service type 'org.xmlpull.v1.XmlPullParserFactory' 09:05:23,445 INFO [org.jboss.web] (ServerService Thread Pool -- 88) JBAS018210: Register web context: /BaseX801 09:05:23,448 ERROR [org.apache.catalina.core] (ServerService Thread Pool -- 88) JBWEB001097: Error starting context /BaseX801: java.lang.IllegalArgumentException: JBWEB000250: Child container with name default already exists at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:794) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:785) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] at org.apache.catalina.core.StandardContext.addChild(StandardContext.java:1862) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] at org.jboss.as.web.deployment.JBossContextConfig.processWebMetaData(JBossContextConfig.java:471) [jboss-as-web-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10] at org.jboss.as.web.deployment.JBossContextConfig.applicationWebConfig(JBossContextConfig.java:201) [jboss-as-web-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10] at org.apache.catalina.startup.ContextConfig.start(ContextConfig.java:354) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:153) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] at org.jboss.as.web.deployment.JBossContextConfig.lifecycleEvent(JBossContextConfig.java:194) [jboss-as-web-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10] at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:115) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] at org.apache.catalina.core.StandardContext.start(StandardContext.java:3717) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1] at org.jboss.as.web.deployment.WebDeploymentService.doStart(WebDeploymentService.java:156) [jboss-as-web-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10] at org.jboss.as.web.deployment.WebDeploymentService.access$000(WebDeploymentService.java:60) [jboss-as-web-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10] at org.jboss.as.web.deployment.WebDeploymentService$1.run(WebDeploymentService.java:93) [jboss-as-web-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10] at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_67] at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_67] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_67] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_67] at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_67] at org.jboss.threads.JBossThread.run(JBossThread.java:122) 09:05:23,469 ERROR [org.apache.catalina.core] (ServerService Thread Pool -- 88) JBWEB001103: Error detected during context /BaseX801 start, will stop it 09:05:23,470 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool -- 88) MSC000001: Failed to start service jboss.web.deployment.default-host./BaseX801: org.jboss.msc.service.StartException in service jboss.web.deployment.default-host./BaseX801: org.jboss.msc.service.StartException in anonymous service: JBAS018040: Failed to start context at org.jboss.as.web.deployment.WebDeploymentService$1.run(WebDeploymentService.java:96) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471) [rt.jar:1.7.0_67] at java.util.concurrent.FutureTask.run(FutureTask.java:262) [rt.jar:1.7.0_67] at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) [rt.jar:1.7.0_67] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) [rt.jar:1.7.0_67] at java.lang.Thread.run(Thread.java:745) [rt.jar:1.7.0_67] at org.jboss.threads.JBossThread.run(JBossThread.java:122) Caused by: org.jboss.msc.service.StartException in anonymous service: JBAS018040: Failed to start context at org.jboss.as.web.deployment.WebDeploymentService.doStart(WebDeploymentService.java:161) at org.jboss.as.web.deployment.WebDeploymentService.access$000(WebDeploymentService.java:60) at org.jboss.as.web.deployment.WebDeploymentService$1.run(WebDeploymentService.java:93) ... 6 more 09:05:23,685 ERROR [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "BaseX801.war" was rolled back with the following failure message: {"JBAS014671: Failed services" => {"jboss.web.deployment.default-host./BaseX801" => "org.jboss.msc.service.StartException in service jboss.web.deployment.default-host./BaseX801: org.jboss.msc.service.StartException in anonymous service: JBAS018040: Failed to start context Caused by: org.jboss.msc.service.StartException in anonymous service: JBAS018040: Failed to start context"}} 09:05:23,766 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015877: Stopped deployment BaseX801.war (runtime-name: BaseX801.war) in 80ms

1 1

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

BaseX-Talk March 2015