[
https://issues.apache.org/jira/browse/JENA-428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13617964#comment-13617964
]
Hudson commented on JENA-428:
-----------------------------
Integrated in Jena__Development_Test #575 (See
[https://builds.apache.org/job/Jena__Development_Test/575/])
Fix JENA-428, allow passing of authentication information for remote
updates using the same srv:serviceContext mechanism supported for queries
This involved refactoring UpdateProcessRemote and UpdateProcessRemoteForm to
use a common base class where the config functionality was placed. There was
also some changes to HttpOp required to enable use of credentials on the actual
HTTP requests. (Revision 1462659)
Result = FAILURE
rvesse :
Files :
* /jena/trunk/jena-arq
*
/jena/trunk/jena-arq/src/main/java/com/hp/hpl/jena/sparql/engine/http/QueryEngineHTTP.java
*
/jena/trunk/jena-arq/src/main/java/com/hp/hpl/jena/sparql/modify/UpdateProcessRemote.java
*
/jena/trunk/jena-arq/src/main/java/com/hp/hpl/jena/sparql/modify/UpdateProcessRemoteBase.java
*
/jena/trunk/jena-arq/src/main/java/com/hp/hpl/jena/sparql/modify/UpdateProcessRemoteForm.java
* /jena/trunk/jena-arq/src/main/java/org/apache/jena/riot/stream/LocatorURL.java
* /jena/trunk/jena-arq/src/main/java/org/apache/jena/riot/web/HttpOp.java
*
/jena/trunk/jena-arq/src/test/java/com/hp/hpl/jena/sparql/engine/http/TestService.java
*
/jena/trunk/jena-fuseki/src/main/java/org/apache/jena/fuseki/servlets/SPARQL_Query.java
> Remote updates do not respect srv:serviceContext
> ------------------------------------------------
>
> Key: JENA-428
> URL: https://issues.apache.org/jira/browse/JENA-428
> Project: Apache Jena
> Issue Type: Improvement
> Components: ARQ
> Affects Versions: Jena 2.10.0
> Reporter: Rob Vesse
> Assignee: Rob Vesse
> Labels: authentication, sparql, update
> Original Estimate: 24h
> Time Spent: 1h
> Remaining Estimate: 23h
>
> This is a follow on issue prompted by JENA-405, that issue requested support
> for respecting the service context for remote SPARQL queries which allowed
> for setting certain parameters in a centralized place rather than every time
> you wanted to access a service.
> It seems reasonable that we should do the same for updates but having looked
> at the code there appears to be no existing way to inject authentication
> parameters for updates. This is a lacking feature since it would seem more
> likely that credentials would be needed for updates than queries.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
