[
https://issues.apache.org/jira/browse/JENA-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15369641#comment-15369641
]
ASF GitHub Bot commented on JENA-576:
-------------------------------------
Github user fpservant commented on the issue:
https://github.com/apache/jena/pull/139
Andy
> Apologies that this has taken so long.
no problem, really. Thanks for this answer. Give me some time to take all
your valuable comments into account.
just one remark:
> I ran the tests for JSONLD but got:
>> 10:13:04 INFO TestJsonLDWriter :: Sorry to get this exception
>>org.apache.jena.riot.RiotException:
com.github.jsonldjava.core.JsonLdError: loading remote context failed:
http://schema.org/
...
> The tests and build should work if there is no extenral connectivity.
I understand the point, and I'll take it into account. But actually, I'm
happy to see this, because it shows that one problem that I had at the time has
been solved. As was noted in a comment in the code:
```
} catch (Throwable e) {
Logger.getLogger(getClass()).info("Sorry to get this
exception",e);
}
// It seems to work, but there's a problem with httpclient version: the
one used by jena
// is not compatible with the one expected by JSONLD-java API. We get
/*
java.lang.NoSuchMethodError:
org.apache.http.impl.client.cache.CacheConfig.custom()Lorg/apache/http/impl/client/cache/CacheConfig$Builder;
```
Looks like the work on " (JENA-576) Upgrade Apache HTTP Client to 4.3" has
solved the issue
> 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)
