[jira] [Commented] (JENA-1090) Add transaction handling convenience code

[ https://issues.apache.org/jira/browse/JENA-1090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15369301#comment-15369301 ] ASF GitHub Bot commented on JENA-1090: -- Github user afs commented on the issue:

[GitHub] jena issue #153: JENA-1090: Txn - a java8-centric transaction API

Github user afs commented on the issue: https://github.com/apache/jena/pull/153 There is markdown documentation to go with this. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature

[jira] [Commented] (JENA-1090) Add transaction handling convenience code

[ https://issues.apache.org/jira/browse/JENA-1090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15369300#comment-15369300 ] ASF GitHub Bot commented on JENA-1090: -- GitHub user afs opened a pull request:

[GitHub] jena pull request #153: JENA-1090: Txn - a java8-centric transaction API

GitHub user afs opened a pull request: https://github.com/apache/jena/pull/153 JENA-1090: Txn - a java8-centric transaction API You can merge this pull request into a Git repository by running: $ git pull https://github.com/afs/jena txn Alternatively you can review and apply

[jira] [Commented] (JENA-576) Upgrade Apache HTTP Client to 4.3

[ https://issues.apache.org/jira/browse/JENA-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15369268#comment-15369268 ] ASF GitHub Bot commented on JENA-576: - Github user ajs6f commented on the issue:

[GitHub] jena issue #151: JENA-576: Moving away from deprecated HttpCommons Client AP...

Github user ajs6f commented on the issue: https://github.com/apache/jena/pull/151 As I understand it (for what that's worth) `HttpContext` is mostly about the idea of a "conversation", so if you've got some kind of session going on, or a series of request-response cycles that compose

[GitHub] jena issue #149: Jena 1206

Github user afs commented on the issue: https://github.com/apache/jena/pull/149 +1 : Looks good to me. --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or

[jira] [Commented] (JENA-576) Upgrade Apache HTTP Client to 4.3

[ https://issues.apache.org/jira/browse/JENA-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15369111#comment-15369111 ] ASF GitHub Bot commented on JENA-576: - Github user afs commented on the issue:

[GitHub] jena issue #151: JENA-576: Moving away from deprecated HttpCommons Client AP...

Github user afs commented on the issue: https://github.com/apache/jena/pull/151 Another thought: Does `HttpContext` with every `HttpClient` usage make an sense now? We now rely on `HttpClient` a lot more and `HttpContext` seems mainly for cookies. Maybe, versions of calls with

[jira] [Commented] (JENA-576) Upgrade Apache HTTP Client to 4.3

[ https://issues.apache.org/jira/browse/JENA-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15369109#comment-15369109 ] ASF GitHub Bot commented on JENA-576: - Github user ajs6f commented on the issue:

[GitHub] jena issue #151: JENA-576: Moving away from deprecated HttpCommons Client AP...

Github user ajs6f commented on the issue: https://github.com/apache/jena/pull/151 I'm not totally clear about the style for `CloseableHttpClient`, either. I'll poke around and see if I can get a better reading on that. And I'll start jotting up some docs. --- If your project is set

[jira] [Commented] (JENA-576) Upgrade Apache HTTP Client to 4.3

[ https://issues.apache.org/jira/browse/JENA-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15369100#comment-15369100 ] ASF GitHub Bot commented on JENA-576: - Github user afs commented on the issue:

[GitHub] jena issue #151: JENA-576: Moving away from deprecated HttpCommons Client AP...

Github user afs commented on the issue: https://github.com/apache/jena/pull/151 I haven't got my head around the new API yet - this is just a preliminary comment. It is a bit of a change around authentication but I think it is the right thing to do. It seems to me that the

[jira] [Resolved] (JENA-1158) Provide unionDefaultGraph for all graphs.

[ https://issues.apache.org/jira/browse/JENA-1158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andy Seaborne resolved JENA-1158. - Resolution: Fixed Assignee: Andy Seaborne Fix Version/s: Jena 3.1.1 > Provide

[jira] [Commented] (JENA-1158) Provide unionDefaultGraph for all graphs.

[ https://issues.apache.org/jira/browse/JENA-1158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15369037#comment-15369037 ] ASF GitHub Bot commented on JENA-1158: -- Github user asfgit closed the pull request at:

[GitHub] jena pull request #152: JENA-1158: Union default graph

Github user asfgit closed the pull request at: https://github.com/apache/jena/pull/152 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is

[jira] [Commented] (JENA-1158) Provide unionDefaultGraph for all graphs.

[ https://issues.apache.org/jira/browse/JENA-1158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15369036#comment-15369036 ] ASF subversion and git services commented on JENA-1158: --- Commit