Re: parse error in fuseki UI when typing a query

2018-11-29 Thread Vincent Ventresque
Many thanks for your patience, these are very useful details. > Can you provide *repeatable examples*? Ideally, not using YASQE. -- unfortunately not... but if I have the same problem, I'll try to configure Jetty and/or Jena error handling (as Marco suggested) to get some more information if I

Re: parse error in fuseki UI when typing a query

2018-11-29 Thread Andy Seaborne
On 29/11/2018 08:03, Vincent Ventresque wrote: Thanks a lot for all these elements Andy. However, I still don't understand /why the parser works most of the time and fails sometimes/. Can you provide repeatable examples? Ideally, not using YASQE. (BTW YASQE retains internal state like last

Re: parse error in fuseki UI when typing a query

2018-11-29 Thread Vincent Ventresque
Hello Marco, Thanks for the link, I'll have a look. Also opened a few javascript files this morning : I wonder if the problem could be linked to 'sparql.js' or 'codemirror.js' ( in webapp/js/lib/ and webapp/js/lib/mode/ ) Le 29/11/2018 à 12:04, Marco Neumann a écrit : one seems to be t

Re: parse error in fuseki UI when typing a query

2018-11-29 Thread Marco Neumann
one seems to be the jetty error + jena error message and the other is the specific jena 'lexical error' message. keep in mind fuseki uses jetty to serve http requests in the standard configuration. since jena is open source you can inspect the error handle in more detail yourself, show more detai

Re: parse error in fuseki UI when typing a query

2018-11-29 Thread Vincent Ventresque
Thanks a lot for all these elements Andy. However, I still don't understand /why the parser works most of the time and fails sometimes/. Any clue about what's happening? I find it very strange that re-typing the same query can solve the problem (I don't change anything but the query string : t

Re: parse error in fuseki UI when typing a query

2018-11-28 Thread Andy Seaborne
The /MyDataset/ is slightly magic. Fuseki inspects the request and determines if it is a query or an update. It is a query if: 1/ The URL query string of the request URI has ?query= in it. (GET or HTML form) 2/ The content type is application/sparql-query (POST) and an update if: 3/ The URL

Re: parse error in fuseki UI when typing a query

2018-11-28 Thread Vincent Ventresque
Thanks Andy. I don't understand : 'update' queries work in UI most of the time (and when I re-write this 'delete' query, it works... Of course I have to give http://localhost:3030/MyDataset or http://localhost:3030/MyDataset/update as endpoint url (above dialog box), not http://localhost:3030

Re: parse error in fuseki UI when typing a query

2018-11-28 Thread Vincent Ventresque
Thanks Andy. I don't understand : 'update' queries work in UI most of the time (and when I re-write this 'delete' query, it works... Of course I have to give http://localhost:3030/MyDataset or http://localhost:3030/MyDataset/update as endpoint url (above dialog box), not http://localhost:3030

Re: parse error in fuseki UI when typing a query

2018-11-28 Thread Andy Seaborne
Vincent, It's a parse because DELETE is SPARQL Update and the query editor is for query. In SPARQL, they are different languages. There is some way (IIRC) to use the UI with update but I can't remember how - maybe someone else can answer that part. Andy On 28/11/2018 11:28, Vincent Ven

parse error in fuseki UI when typing a query

2018-11-28 Thread Vincent Ventresque
Hello, Sometimes I have a '400 Parse error' when typing a query in Fuseki UI. -- Here, the query string 'delete {?s ?p ?o } where {?s ?p ?o }' doesn't work at first. N.B.: I hadn't pasted the string from other software, everything had been typed in the query dialog box. -- If I change the strin