As an additional note I just tried using DROP GRAPH on the /update endpoint
as an alternative to HTTP DELETE and that doesn't remove the Graph either.

Rob

On Thu, 27 Jan 2011 09:33:52 +0000, Rob Vesse <[email protected]>
wrote:
> Hi all 
> 
> I've coded up some simple unit tests to test the Fuseki support
> in my library and noticed that HTTP DELETE does not seem to work. 
> 
> I use
> PUT in my code to add a Graph and can see it via the /data endpoint of
> Fuseki 
> 
> I use GET in my code to retrieve the Graph to check it is stored
> correctly which it is 
> 
> I then try and use DELETE to remove the Graph but I
> get a 204 No Content response - according to the Uniform HTTP Protocol
spec
> I should get a 200/202 to indicate success. But if I subsequently do a
GET
> then the Graph is still present in the dataset so DELETE has apparently
not
> worked. 
> 
> Is this a bug or related to my dataset. I am using the default
> in-memory dataset and running Fuseki using the following command: 
> 
> java
> -jar fuseki-0.1.0-server.jar --update --mem /dataset 
> 
> The log trace looks
> this: 
> 
> 09:30:30 INFO Fuseki :: Dataset: in-memory
> 09:30:30 INFO Fuseki ::
> Update enabled
> 09:30:30 INFO Fuseki :: Fuseki 0.1.0
> 09:30:30 INFO Fuseki ::
> Jetty 7.x.y-SNAPSHOT
> 09:30:30 INFO Fuseki :: Dataset = /dataset
> 09:30:30
> INFO Fuseki :: Started 2011/01/27 09:30:30 GMT on port 3030
> 09:30:35 INFO
> Fuseki :: [1] PUT
>
http://localhost:3030/dataset/data?graph=http%3A%2F%2Fexample.org%2FfusekiTest
> 09:30:35
> INFO Fuseki :: [1] 201 Created
> 09:30:35 INFO Fuseki :: [2] DELETE
>
http://localhost:3030/dataset/data?graph=http%3A%2F%2Fexample.org%2FfusekiTest
> 09:30:35
> INFO Fuseki :: [2] 204 No Content 
> 
> By the way is there a reason that GET
> requests aren't in the log trace? I notice that if I do a SPARQL Query to
> the /query endpoint it appears in the trace so why not a GET to the /data
> endpoint? 
> 
> I can provide code if desired but the code is all in C# so not
> necessarily very helpful to you for debugging purposes. If you need
further
> information to investigate this please let me know. 
> 
> Rob Vesse

-- 
PhD Student
IAM Group
Bay 20, Room 4027, Building 32
Electronics & Computer Science
University of Southampton

Reply via email to