On 15/03/12 18:13, Stephen Allen wrote:
-1
The control panel is broken for me in the default install. Steps to reproduce:
wget
https://repository.apache.org/content/repositories/orgapachejena-071/org/apache/jena/jena-fuseki/0.2.1-incubating/jena-fuseki-0.2.1-incubating-distribution.tar.gz
tar xfvz jena-fuseki-0.2.1-incubating-distribution.tar.gz
cd jena-fuseki-0.2.1-incubating
./fuseki-server --update --mem /dataset
I then browse to "http://localhost:3030/control-panel.tpl";. I see
"/dataset" in the combo box and I press the "Select" button. I get
the following results:
Error 400: No query string
Fuseki - version 0.2.1-incubating (Build date: 2012-03-13T09:35:00+0000)
Ah - OK - The problem is that /dataset is both a special name (the name
of an action that sets the session state to indicate the dataset) and in
this setup the name of the dataset. For any dataset DA, /DA is routed
to the graph store protocol in expectation that the dataset URI is also
the graph store protocol service URI.
This only affects a dataset called "/dataset", only if using the UI forms.
What do you think the important case is? Let's design for that and fit
other names around it. One possibility is that all service URIs start $
or "_" or even "/$/"
Other services include
/validate/query
/validate/update
/validate/iri
/validate/data
The management services have been moves to another port. It's just the
UI services left.
Also, SPARQLer ("http://localhost:3030/sparql.html";) doesn't seem to
work either:
Error 400: No dataset description in protocol request or in the query string
Fuseki - version 0.2.1-incubating (Build date: 2012-03-13T09:35:00+0000)
I get a webpage if I go to sparql.html.
If, then, I press "Get Results" then I get that message. The message is
correct though - this is the general purpose query engine at "/sparql"
and needs some data to query, either with FROM or default-graph-uri etc.
If you don't specify the data to query then the general purpose QE has
nothing to query. 400 is "bad request" i.e. client error.
The command line s-* tools however seem to work fine when I use commands like:
./s-put http://localhost:3030/dataset/data default test.nt
./s-query --service http://localhost:3030/dataset/query 'SELECT * {?s ?p ?o}'
-Stephen
Andy
On Thu, Mar 15, 2012 at 10:28 AM, Robert Vesse<[email protected]> wrote:
Looks good
+1
Rob
On Mar 14, 2012, at 12:11 AM, Paolo Castagna wrote:
Andy Seaborne wrote:
The mod
