You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by "Paolo Castagna (Resolved) (JIRA)" <ji...@apache.org> on 2012/01/30 17:44:10 UTC

[jira] [Resolved] (JENA-195) Allow users to specify query parameters when they use SERVICE <...?name=value> in their SPARQL queries

     [ https://issues.apache.org/jira/browse/JENA-195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paolo Castagna resolved JENA-195.
---------------------------------

       Resolution: Fixed
    Fix Version/s: ARQ 2.9.1
    
> 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
>             Fix For: ARQ 2.9.1
>
>         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