Your config file looks fine to me - two services over the same dataset.
It's two services because SPARQL update and SPARQL query are different
languages (and you can protect the update endpoint separately from the
query endpoint - no injection attacks on the query service). It looks to
me like a Joseki bug in the internal locking.
Andy
On 12/05/11 09:37, Michael Brunnbauer wrote:
re
On Wed, May 11, 2011 at 09:45:49PM +0100, Andy Seaborne wrote:
Yes. The dataset has a SPARQL and an update service. Is it possible to
configure a service that can do both ?
Yes - it's supposed to work.
I have studied http://www.joseki.org/configuration.html and
joseki-config-example.ttl but don't know how to do it. Maybe by specifying
2x joseki:processor in the service ?
joseki:processor joseki:ProcessorSPARQL_FixedDS ;
joseki:processor joseki:ProcessorSPARQLUpdate ;
Or 2x module:implementation in the processor ?
module:implementation joseki:ImplSPARQL ;
module:implementation joseki:ImplSPARQLUpdate ;
Or 2x module:className in the implementation ?
module:className<java:org.joseki.processors.SPARQL> ;
module:className<java:org.joseki.processors.SPARQLUpdate> ;
Please help.
cu,
brunni
