incubator-jena-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (Commented) (JIRA)" <>
Subject [jira] [Commented] (JENA-195) Allow users to specify query parameters when they use SERVICE <...?name=value> in their SPARQL queries
Date Mon, 30 Jan 2012 16:20:10 GMT


Hudson commented on JENA-195:

Integrated in Jena_ARQ #430 (See [])

HttpQuery and QueryEngineHTTP consistently throw a QueryExecException exception if a 'query'
parameter is specified with SERVICE.
Added a couple of examples (i.e. ExampleDBPedia2|3) to show the two ways to specify a query
parameter with SERVICE.

I hope everything is fine now. If not, let me know and I'll fix it directly in trunk.

castagna : 
Files : 
* /incubator/jena/Jena2/ARQ/trunk/ChangeLog.txt
* /incubator/jena/Jena2/ARQ/trunk/src-examples/arq/examples/
* /incubator/jena/Jena2/ARQ/trunk/src-examples/arq/examples/
* /incubator/jena/Jena2/ARQ/trunk/src/main/java/com/hp/hpl/jena/query/
* /incubator/jena/Jena2/ARQ/trunk/src/main/java/com/hp/hpl/jena/sparql/engine/http/
* /incubator/jena/Jena2/ARQ/trunk/src/main/java/com/hp/hpl/jena/sparql/engine/http/
* /incubator/jena/Jena2/ARQ/trunk/src/main/java/com/hp/hpl/jena/sparql/engine/http/

> Allow users to specify query parameters when they use SERVICE <...?name=value>
in their SPARQL queries
> ------------------------------------------------------------------------------------------------------
>                 Key: JENA-195
>                 URL:
>             Project: Jena
>          Issue Type: Improvement
>          Components: ARQ
>            Reporter: Paolo Castagna
>            Assignee: Paolo Castagna
>            Priority: Minor
>         Attachments: JENA-195.patch, JENA-195.patch, JENA-195.patch
>   Original Estimate: 8h
>  Remaining Estimate: 8h
> SPARQL endpoints might require or allow additional query parameters, if we want to use
those endpoints with SERVICE <...> in SPARQL queries we must support query parameters
and allow users to use SERVICE <...?name=value> in their SPARQL queries.
> can look in the Context for additional parameters. 
> Parameters need to be kept separate and grouped on a per SERVICE endpoint basis (in order
to avoid exposing parameter values to wrong places).
> A Map<String, Map<String,List<String>>> can be uses to map SERVICE
endpoint URLs to parameter-->values.
> probably needs to change (to keep the parameters separate from the SERVICE
endpoint URL).
> See also this thread on jena-users:

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message