HTTP error code 403 means the client does not have access to the requested resource: http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.4
On Thu, Jan 29, 2015 at 2:57 AM, Trevor Donaldson <[email protected]> wrote: > Trying to use DatasetAccessor. I am getting the following error. Where > could I start to troubleshoot this error. Is this a problem with my > config.ttl file? I am trying to run the following command : > > DatasetAccessor datasetAccessor = > DatasetAccessorFactory.createHTTP("http://localhost:3030/ds";); > Model model = datasetAccessor.getModel("http://example.org/#serviceA";); > > > Exception in thread "main" org.apache.jena.atlas.web.HttpException: 403 - > Forbidden: SPARQL Graph Store Protocol : Read operation : GET > at org.apache.jena.riot.web.HttpOp.exec(HttpOp.java:1118) > at org.apache.jena.riot.web.HttpOp.execHttpGet(HttpOp.java:385) > at org.apache.jena.riot.web.HttpOp.execHttpGet(HttpOp.java:354) > at > org.apache.jena.web.DatasetGraphAccessorHTTP.doGet(DatasetGraphAccessorHTTP.java:134) > at > org.apache.jena.web.DatasetGraphAccessorHTTP.httpGet(DatasetGraphAccessorHTTP.java:128) > at org.apache.jena.web.DatasetAdapter.getModel(DatasetAdapter.java:47) > at com.security.examples.FusekiExample.main(FusekiExample.java:13) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:483) > at com.intellij.rt.execution.application.AppMain.main(AppMain.java:134) > > On Wed, Jan 28, 2015 at 3:07 PM, Trevor Donaldson <[email protected]> > wrote: > >> I would prefer to use the model api. There is reification, deletion, >> inserting, etc.... I will take a look at the DatasetAccessor. I am only >> applying changes to a named graph. >> >> On Wed, Jan 28, 2015 at 2:44 PM, Rob Vesse <[email protected]> wrote: >> >>> Via Fuseki >>> >>> Attempting to do anything that bypasses Fuseki and accesses the TDB data >>> directory directly is ill-advised, shouldn't work (there is process level >>> locking on TDB data directories) and is highly likely to corrupt your >>> data. >>> >>> One option would be to use SPARQL updates to supply your changes. >>> >>> However if your changes involve complex graph manipulations best done with >>> the Model API AND they only apply to a specific named graph then you could >>> use the graph store protocol to replace an existing named model - see >>> DatasetAccessor which is the Jena API to the protocol and its methods such >>> as getModel() and putModel() >>> >>> Rob >>> >>> On 28/01/2015 10:58, "Trevor Donaldson" <[email protected]> wrote: >>> >>> >Hi all, >>> > >>> >What would be the best way to update a TDB store behind Fuseki. I have a >>> >standalone app that needs to update (delete and insert) statements as >>> well >>> >as insert new statements. I was thinking that I could use the Jena api >>> >with >>> >an in memory model and then somehow send the deletes first to fuseki, >>> then >>> >send the inserts to fuseki. Not exactly sure how to accomplish this. Is >>> >this possible? >>> > >>> >Thanks, >>> >Trevor >>> >>> >>> >>> >>> >>
