[
https://issues.apache.org/jira/browse/JENA-195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13196201#comment-13196201
]
Hudson commented on JENA-195:
-----------------------------
Integrated in Jena_ARQ #430 (See [https://builds.apache.org/job/Jena_ARQ/430/])
JENA-195
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/ExampleDBpedia2.java
* /incubator/jena/Jena2/ARQ/trunk/src-examples/arq/examples/ExampleDBpedia3.java
* /incubator/jena/Jena2/ARQ/trunk/src/main/java/com/hp/hpl/jena/query/ARQ.java
*
/incubator/jena/Jena2/ARQ/trunk/src/main/java/com/hp/hpl/jena/sparql/engine/http/HttpQuery.java
*
/incubator/jena/Jena2/ARQ/trunk/src/main/java/com/hp/hpl/jena/sparql/engine/http/QueryEngineHTTP.java
*
/incubator/jena/Jena2/ARQ/trunk/src/main/java/com/hp/hpl/jena/sparql/engine/http/Service.java
> Allow users to specify query parameters when they use SERVICE
> <...?name=value> in their SPARQL queries
> ------------------------------------------------------------------------------------------------------
>
> Key: JENA-195
> URL: https://issues.apache.org/jira/browse/JENA-195
> 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.
> Service.java 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.
> OpService.java probably needs to change (to keep the parameters separate from
> the SERVICE endpoint URL).
> See also this thread on jena-users:
> http://markmail.org/thread/wc5hvr3b3uzy2mrk
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
