[
https://issues.apache.org/jira/browse/JENA-422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13613190#comment-13613190
]
Andy Seaborne edited comment on JENA-422 at 3/25/13 10:14 PM:
--------------------------------------------------------------
I'm now getting several (12) warnings of
21:38:28 WARN Query :: setResultVars(): no query pattern
from the test suite in OpAsQueryTest. This happens when OpAsQueryTest is run
on it own as well as in the full suite.
The query pattern is indeed null.
was (Author: andy.seaborne):
I'm now getting several (12) warnigns of
21:38:28 WARN Query :: setResultVars(): no query pattern
from the test suite in OpAsQueryTest. This happens when OpAsQueryTest is run
on it own as well as in the full suite.
The query pattern is indeed null.
> SERVICE execution does not propogate BINDs within the SERVICE clause
> --------------------------------------------------------------------
>
> Key: JENA-422
> URL: https://issues.apache.org/jira/browse/JENA-422
> Project: Apache Jena
> Issue Type: Bug
> Components: ARQ
> Affects Versions: Jena 2.10.0
> Reporter: Rob Vesse
> Assignee: Rob Vesse
> Labels: federation, service, sparql
> Fix For: Jena 2.10.1
>
>
> This was originally spotted thanks to a user question at
> http://answers.semanticweb.com/questions/21759/using-bind-and-service-in-fuseki
> The basic problem described there is that a BIND used within a SERVICE clause
> appeared to have no effect.
> I was able to reproduce this with a minimal Fuseki setup using an in-memory
> dataset containing a single triple and the following query:
> SELECT * WHERE { SERVICE <http://localhost:3030/ds/query> { ?s ?p ?o .
> BIND(?o AS ?x) } }
> I have a unit test for Fuseki that demonstrates the behaviour as well. Under
> the debugger I can see that the BIND clause is not included in the query
> string that gets sent to the remote service hence the lack of values for the
> BINDed variable.
--
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
