[
https://issues.apache.org/jira/browse/JENA-1332?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen Owens updated JENA-1332:
Attachment: JenaFilterNotExistsUnionTest.java
> Possibly incorrect results from SPARQL with union and
Stephen Owens created JENA-1332:
---
Summary: Possibly incorrect results from SPARQL with union and
filter not exists
Key: JENA-1332
URL: https://issues.apache.org/jira/browse/JENA-1332
Project: Apache Jen
HttpClientContext does seem to have an "adapt" function as its main use
(I'm only going by the javadoc "Adaptor class ..."). The "Client" is a
throwing in a hint that is a bit strange as HttpContext goes with
HttpClient.
Mixing the two gets into yuky-ness if the application provides a
HttpCo
I think this is indeed where we are getting to (that client and context need to be fully threaded through the whole API). That's kind of the price we pay to
avoid doing lots and lots of work to hide them.
I'm not as sure that context without client works as well... but it does seem
from the HTT
I think this is indeed where we are getting to (that client and context need to be fully threaded through the whole API). That's kind of the price we pay to
avoid doing lots and lots of work to hide them.
I'm not as sure that context without client works as well... but it does seem
from the HTT
[
https://issues.apache.org/jira/browse/JENA-1331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15986654#comment-15986654
]
Russell Morrisey edited comment on JENA-1331 at 4/27/17 1:56 PM:
[
https://issues.apache.org/jira/browse/JENA-1331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15986654#comment-15986654
]
Russell Morrisey edited comment on JENA-1331 at 4/27/17 1:55 PM:
[
https://issues.apache.org/jira/browse/JENA-1331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15986654#comment-15986654
]
Russell Morrisey commented on JENA-1331:
I would like to specify default query stri
[
https://issues.apache.org/jira/browse/JENA-1331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15986654#comment-15986654
]
Russell Morrisey edited comment on JENA-1331 at 4/27/17 1:54 PM:
Github user ajs6f commented on the issue:
https://github.com/apache/jena/pull/133
NP, @CesarPantoja. If your work concerned Jena, please feel free to let the
list know about it. It's good to share good news.
---
If your project is set up for it, you can reply to this email and have
[
https://issues.apache.org/jira/browse/JENA-1330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15986601#comment-15986601
]
ASF GitHub Bot commented on JENA-1330:
--
GitHub user afs opened a pull request:
ht
GitHub user afs opened a pull request:
https://github.com/apache/jena/pull/247
Query string in URLs; uniform HttpClient/HttpContext usage.
JENA-1330: pass HttpClient/HttpContext in query and update calls.
JENA-1331: Support additional query string in URLs for services.
(triggered by the question on users@ about RDFConnection and HttpClient
=> JENA-1330)
Q:
For API operations that take an HttpClient argument, should there always
be a variant that accepts an HttpClient and a HttpContext?
From looking at the code, there is also a possible HttpContext to apply
Andy Seaborne created JENA-1331:
---
Summary: RDFConnectionRemote does not handle additional query
string items in GSP operations.
Key: JENA-1331
URL: https://issues.apache.org/jira/browse/JENA-1331
Projec
Andy Seaborne created JENA-1330:
---
Summary: RDFConnectionRemote.query does not pass on the HttpClient
Key: JENA-1330
URL: https://issues.apache.org/jira/browse/JENA-1330
Project: Apache Jena
Iss
15 matches
Mail list logo
