Hi again,

in case it can help, I got back to a version that doesn't throw any 1012
exception.
The only one difference I see is that I had removed the &callback=? in the
query

+++
Maud


*Doesn't throw any 1012 :*

// loading the lexique
    window.onload = function() {
        $.ajax({
            dataType: "json",
            url: '
http://devictio:devictio@basex.tge-adonis.fr/rest/DonLexique',
            data : "method=jsonml&query=//list&callback=?",

            beforeSend: function(xhr) {
                // doesn't work, requires auth in the url...
                //xhr.setRequestHeader("Authentication", "Basic " +
Base64.encode("devictio:devictio"));
                xhr.setRequestHeader( "ContentType" , "application/json" );
            }, //may need to use "Authorization" instead
            error: function(jqXHR, textStatus, errorThrown){
                alert(textStatus + ": " + errorThrown);
            },
            success: function(result){
                alert("ok ! " + result);
                // fabriquer l'arbre dépliable avec liens cliquables
            }

        });

*Throws a 1012 :*

// loading the lexique
    window.onload = function() {
        $.ajax({
            dataType: 'json',
            url: '
http://devictio:devictio@basex.tge-adonis.fr/rest/DonLexique',
            data : 'query=//list&method=jsonml',
            beforeSend: function(xhr) {
                // doesn't work, requires auth in the url...
                // xhr.setRequestHeader("Authorization", "Basic " +
Base64.encode("devictio:devictio"));
                xhr.setRequestHeader("Content-Type", "application/json");
                //xhr.overrideMimeType("application/j-son;charset=UTF-8");

            }, //May need to use "Authorization" instead
            error: function(jqXHR, textStatus, errorThrown){
                alert(textStatus + " " + errorThrown);
            },
            success: function(result){
                alert("ok ! " + result);
                // fabriquer l'arbre dépliable avec liens cliquables
            }

        });

    };

On Wed, Nov 30, 2011 at 11:24 AM, Maud Ingarao <maud.ingarao@ens-lyon.fr>wrote:

> Hello everybody,
>
> I am very new at BaseX http server, and at jQuery, and at this mailing
> list too :)
>
> Concerning the error you got Colin :
> thrown error: [Exception... "Access to restricted URI denied"  code:
> "1012"...
>
> I suddenly have the same problem though basex and my files have the same
> domain :
> http://hyperdonat.tge-adonis.fr/basex/basex.html
> (The basex server is here : http://basex.tge-adonis.fr/rest)
>
> I had other problems before this with my script, but not this one, and I
> don't know what I did that produced it...
>
> Maud
>
>
>
> On Fri, Oct 21, 2011 at 12:00 PM, <
> basex-talk-request@mailman.uni-konstanz.de> wrote:
>
>> Send BaseX-Talk mailing list submissions to
>>        basex-talk@mailman.uni-konstanz.de
>>
>> To subscribe or unsubscribe via the World Wide Web, visit
>>        https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk
>> or, via email, send a message with subject or body 'help' to
>>        basex-talk-request@mailman.uni-konstanz.de
>>
>> You can reach the person managing the list at
>>        basex-talk-owner@mailman.uni-konstanz.de
>>
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of BaseX-Talk digest..."
>>
>>
>> Today's Topics:
>>
>>   1. Re: Performance of Basex 7.0 XQuery execution (Christian Gr?n)
>>   2. Re: Performance of Basex 7.0 XQuery execution (Jan Vl?insk? (CAD))
>>   3. Clustering/replicating? (Pascal Heus)
>>   4. Re: ajax and http server - cross-domain,  jsonp or proxy?
>>      (colin mcenearney)
>>
>>
>> ----------------------------------------------------------------------
>>
>> Message: 1
>> Date: Thu, 20 Oct 2011 15:43:50 +0200
>> From: Christian Gr?n <christian.gruen@gmail.com>
>> To: Constantine Hondros <Constantine.Hondros@tomtom.com>
>> Cc: "basex-talk@mailman.uni-konstanz.de"
>>        <basex-talk@mailman.uni-konstanz.de>
>> Subject: Re: [basex-talk] Performance of Basex 7.0 XQuery execution
>> Message-ID:
>>        <
>> CAP94bnPYC2abLTiQJkBPt1_WquH6ix8OQeU6HnJtxCa+cp-5Vg@mail.gmail.com>
>> Content-Type: text/plain; charset=ISO-8859-1
>>
>> Hi Constantine,
>>
>> > The XPath I showed was just a simple example of using the
>> preceding-sibling axis.
>>
>> I guessed so already.. Thanks for persisting ;)
>>
>> > I guess what I am asking is ... while most XPath queries I run are
>> quick to resolve, anything using preceding::, preceding-sibling:: or
>> following::, following-sibling:: essentially runs too slowly to be workable
>> - at least, on my sample dataset with about 100K sibling children of the
>> root element.
>> >
>> > So is this any sort of known issue? Should I be looking at any sort of
>> configuration options? Is there any way to profile the execution of the
>> Xpath?
>>
>> It's true that BaseX is mostly optimized for descendant and ancestor
>> operations. In particular, the preceding/preceding-sibling axes will
>> always be slower, as our storage does not contain backward pointers to
>> preceding nodes. I'm pretty sure, though, that there are ways to
>> either optimize relevant queries or the internal optimizer strategies,
>> but we'll probably have to spend some more time on analyzing the
>> relevant bottlenecks..
>>
>> Feel free to ask for more,
>> Christian
>>
>>
>> ------------------------------
>>
>> Message: 2
>> Date: Thu, 20 Oct 2011 19:20:29 +0200
>> From: Jan Vl?insk? (CAD) <jan.vlcinsky@cad-programs.com>
>> To: Christian Gr?n <christian.gruen@gmail.com>
>> Cc: "basex-talk@mailman.uni-konstanz.de"
>>        <basex-talk@mailman.uni-konstanz.de>
>> Subject: Re: [basex-talk] Performance of Basex 7.0 XQuery execution
>> Message-ID:
>>        <CAAq9E_fb5KymrtL=xosGsH=
>> BuP4aWpgip0OWxDJUAHANqqO1Ng@mail.gmail.com>
>> Content-Type: text/plain; charset="utf-8"
>>
>> Hi Constantine
>> Just my side note.
>> As far as I remember, I found this sort of performance discussion with
>> most
>> the XQuery processors I have tested (Sedna, Zorba, Saxon, eXist...). Each
>> time related to sibling, preceding etc. and each time explaining, that
>> indices are not containing pointers for tracking this relationship. My
>> feeling is, this could lead to much bigger index file and slower
>> performance
>> when adding documents and indexing.
>> My conlcusion is - optimizing this sort of queries has its cost and mostly
>> it is better (and somehow possible) to avoid these constructions.
>>
>> With best regards
>>
>> Jan
>>
>> *Ing. Jan Vl?insk?*
>> CAD programy
>> Slune?nicov? 338/3, 734 01 Karvin? R?j, Czech Republic
>> tel: +420-597 602 024; mob: +420-608 979 040
>> skype: janvlcinsky; GoogleTalk: jan.vlcinsky@gmail.com
>> http://cz.linkedin.com/in/vlcinsky
>>
>>
>>
>> On 20 October 2011 15:43, Christian Gr?n <christian.gruen@gmail.com>
>> wrote:
>>
>> > Hi Constantine,
>> >
>> > > The XPath I showed was just a simple example of using the
>> > preceding-sibling axis.
>> >
>> > I guessed so already.. Thanks for persisting ;)
>> >
>> > > I guess what I am asking is ... while most XPath queries I run are
>> quick
>> > to resolve, anything using preceding::, preceding-sibling:: or
>> following::,
>> > following-sibling:: essentially runs too slowly to be workable - at
>> least,
>> > on my sample dataset with about 100K sibling children of the root
>> element.
>> > >
>> > > So is this any sort of known issue? Should I be looking at any sort of
>> > configuration options? Is there any way to profile the execution of the
>> > Xpath?
>> >
>> > It's true that BaseX is mostly optimized for descendant and ancestor
>> > operations. In particular, the preceding/preceding-sibling axes will
>> > always be slower, as our storage does not contain backward pointers to
>> > preceding nodes. I'm pretty sure, though, that there are ways to
>> > either optimize relevant queries or the internal optimizer strategies,
>> > but we'll probably have to spend some more time on analyzing the
>> > relevant bottlenecks..
>> >
>> > Feel free to ask for more,
>> > Christian
>> > _______________________________________________
>> > BaseX-Talk mailing list
>> > BaseX-Talk@mailman.uni-konstanz.de
>> > https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk
>> >
>>