Re: [basex-talk] Multiple basex webapps in same Tomcat

Hi Marco It seems you haven't got an answer yet. As I have never tried to run BaseX with Tomcat personally, I am sorry I can't give real advice on that. Have you ben successful so far? What happens if the RESTXQ code in your second BaseX instance is buggy (..maybe it isn't parsed at all)?

Re: [basex-talk] Difference in query behavior between BaseX 7.7 beta and BaseX 7.8.2

Hi Srinivasan, thanks for your excellent error feedback. First, I thought of the same issue reported by Marco, but it seems that the error still exists. I will have at this today. By the way, we will try our best to release 7.9 until end of June. Best regards, Christian On Sat, Jun 14, 2014

Re: [basex-talk] Multiple basex webapps in same Tomcat

Thanks Christian, if I deploy my code in two different instances of tomcat everything works as expected. The restxq code has been stable and frozen for months so I'm rather sure it's ok. It looks like there is some kind of singleton behaviour that overwrites the loading of the code of the two

Re: [basex-talk] Difference in query behavior between BaseX 7.7 beta and BaseX 7.8.2

Hi Srinivasan, I found out that we prevented the inlining of let clauses with XML constructors some times in order to tackle some namespace bugs. The following query.. let $x := X/ return X xmlns='xx'{ $x/self::X }/X ..would be evaluated in a wrong way when inlining X/. The current

Re: [basex-talk] Strategies for checkout or explicit file locking

Dear Alister, I wonder what strategies other people use to lock a file for “editing”, or “checkout” a file so that only a single user has access (in a multi-user environment). We usually apply the XQuery locking options [1]: From all XQuery expressions that reference the same lock string,

[basex-talk] Basex 404

I've recently run into a problem with basexserver/basexhttp. The host:8984 responds but seems to have lost contact with the webapp directory. Here is what is happening on 3 out of 5 installations (on linux - installed by unpacking the latest ziparchive), where one used to work as expected: 1)

Re: [basex-talk] Basex 404

Hi Lars, could it be that the webapp directory was renamed or moved while the server was running? Otherwise, I have no idea how this could happen (it didn't happen in our Linux instances so far). Christian On Mon, Jun 16, 2014 at 3:00 PM, Lars Johnsen yoon...@gmail.com wrote: I've recently

Re: [basex-talk] RESTXQ declare base-uri .;

Hi Andy, I agree that relative base-uri declarations should always refer to the location of the current query file, no matter in which context. This should be fixed in the latest snapshot [1]. Thanks, Christian On Sun, Jun 15, 2014 at 12:25 AM, Andy Bunce bunce.a...@gmail.com wrote: Hi, It

Re: [basex-talk] RESTXQ declare base-uri .;

Thanks, I will give it a go. My motivation is to find a restxq config that avoids the parsing tax. I am thinking of trying setting RESTXQPATH to restxq. Then using this structure: webapp -app1 --mod2.xqm -restxq --app1 ---restmod1.xqm -static --app1 ---index.html Where restxq/app/restmod1.xqm

Re: [basex-talk] RESTXQ declare base-uri .;

My motivation is to find a restxq config that avoids the parsing tax. Did you already try to move all non-restxq modules into the repository? That's what we usually do. Pre-compilation will fix various of the problems, too (but this is still on our list, and non-trivial..). Christian On

Re: [basex-talk] RESTXQ declare base-uri .;

Did you already try to move all non-restxq modules into the repository? I am sure that works but it does not seem the right use of the repository to me, particularly if those modules start to reference other non xqm files. /Andy On 16 June 2014 16:07, Christian Grün christian.gr...@gmail.com

Re: [basex-talk] RESTXQ declare base-uri .;

I hesitate to suggest this given the recent thread about xquery file extensions :-), but an alternative solution to this might be to expose the extensions used for by restxq scan as a config option. I guess this currently is *.xqm *.xq. If I could set this to, for example, *.xqa, for xquery active

Re: [basex-talk] RESTXQ declare base-uri .;

;) What about adding a .tmp extension to temporarily inactive files? On Tue, Jun 17, 2014 at 12:13 AM, Andy Bunce bunce.a...@gmail.com wrote: I hesitate to suggest this given the recent thread about xquery file extensions :-), but an alternative solution to this might be to expose the

Re: [basex-talk] RESTXQ declare base-uri .;

;) There is something special about RESTXQ files in that they have an effect on the system behavior beyond just being available for potential execution. And one could imagine extending this to other areas where by other annotations hook in to system functions e.g. CRONXQ, EVENTXQ. Why not an