[
https://issues.apache.org/jira/browse/JENA-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15558179#comment-15558179
]
ASF GitHub Bot commented on JENA-576:
-------------------------------------
Github user afs commented on the issue:
https://github.com/apache/jena/pull/151
Should we take a step back and reconsider whether updating the current API
in HttpOp is the right thing to do.
Maybe we ought to
* introduce a different style more fluid
* reconsider a design where the caller is responsible for setting up more
of the `HttpClient` and `HttpOp` provides operations for nothing special (no
auth) + ops that use a redefined `HttpClient`. This is to reduce method bloat.
On (1): something like (quick sketch)
HttpOp.get("http://example/";)
.setAccept("application/rdf-xml") // Override default
.setHttpClientBuilder(....) // Usually no needed, for special
setup only
.exec() ;
where there are implicit builder objects from, `.get(url)`, `.post(url)`,
`.put(url)`, `'delete(url)`.
> Upgrade Apache HTTP Client to 4.3
> ---------------------------------
>
> Key: JENA-576
> URL: https://issues.apache.org/jira/browse/JENA-576
> Project: Apache Jena
> Issue Type: Dependency upgrade
> Components: ARQ
> Affects Versions: Jena 2.11.0
> Reporter: Rob Vesse
> Assignee: Rob Vesse
> Priority: Minor
> Original Estimate: 72h
> Remaining Estimate: 72h
>
> As of 2.11.0 ARQ centralizes all HTTP operations through HttpOp which relies
> on Apache HTTP Client. Currently we are using 4.2.3 while the latest stable
> release is actually 4.3.1
> Therefore we should look at upgrading our code to use the latest version
> which may entail some refactoring since there appears to have been some
> breaking changes across the minor version bump which users have seen in usage
> - e.g.
> https://github.com/pyvandenbussche/sparqles/issues/9#issuecomment-27220738
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
