Remote access from Jena without SNARL

Bart van Leeuwen

unread,

Nov 11, 2016, 5:34:25 AM11/11/16

to Stardog

Hi,

I'm using Jena to connect to a remote Stardog Server, I use the snarl:// uri notation in the server() function parameters.
now with version 4.2 I get the warning that snarl:// will be deprecated, I've tried putting http:// in the uri for the remote server but that doesn't work.

Any hints would be appreciated

Bart

Evren Sirin

unread,

Nov 14, 2016, 6:58:43 AM11/14/16

to sta...@clarkparsia.com

Replacing snarl:// with http:// in the connection string should work without any other changes. What is not working exactly?

Best,

Evren

--
-- --
You received this message because you are subscribed to the C&P "Stardog" group.
To post to this group, send email to sta...@clarkparsia.com
To unsubscribe from this group, send email to
stardog+unsubscribe@clarkparsia.com
For more options, visit this group at
http://groups.google.com/a/clarkparsia.com/group/stardog?hl=en

Bart van Leeuwen

unread,

Nov 14, 2016, 7:43:57 AM11/14/16

to Stardog

this is what I run into:

13:40:00 WARN RDFWriterRegistry         :: New service class com.complexible.common.rdf.rio.writer.TurtleWriterFactory replaces existing service class org.openrdf.rio.turtle.TurtleWriterFactory
SEVERE - EjbTransactionUtil.handleSystemException: org.apache.http.impl.client.DefaultHttpClient.execute(Lorg/apache/http/HttpHost;Lorg/apache/http/HttpRequest;Lorg/apache/http/protocol/HttpContext;)Lorg/apache/http/client/methods/CloseableHttpResponse;
java.lang.NoSuchMethodError: org.apache.http.impl.client.DefaultHttpClient.execute(Lorg/apache/http/HttpHost;Lorg/apache/http/HttpRequest;Lorg/apache/http/protocol/HttpContext;)Lorg/apache/http/client/methods/CloseableHttpResponse;
    at com.complexible.stardog.protocols.http.client.BaseHttpClient.executeRaw(BaseHttpClient.java:318)
    at com.complexible.stardog.protocols.http.client.BaseHttpClient.execute(BaseHttpClient.java:303)
    at com.complexible.stardog.protocols.http.client.HttpClientImpl.connect(HttpClientImpl.java:212)
    at com.complexible.stardog.protocols.http.client.HttpClientImpl.connect(HttpClientImpl.java:93)
    at com.complexible.stardog.protocols.http.client.HttpConnection.create(HttpConnection.java:44)
    at com.complexible.stardog.protocols.http.client.HttpDriver.connect(HttpDriver.java:75)
    at com.complexible.stardog.api.DriverManager.getConnection(DriverManager.java:74)
    at com.complexible.stardog.api.ConnectionConfiguration.connect(ConnectionConfiguration.java:126)

I'm not sure what to think of that.

( compiled against stardog-jena 4.2 )

Op maandag 14 november 2016 12:58:43 UTC+1 schreef Evren Sirin:

Michael Grove

unread,

Nov 14, 2016, 7:59:50 AM11/14/16

to stardog

Jena and Stardog have different dependencies for the Apache HttpClient library, which is causing a problem with your classpath. I think Jena is using 4.2 whereas Stardog is using 4.4.

Cheers,

Mike

--

Bart van Leeuwen

unread,

Nov 14, 2016, 8:01:29 AM11/14/16

to Stardog

That was my impression as well, now the question is how to solve this.

Op maandag 14 november 2016 13:59:50 UTC+1 schreef Michael Grove:

stardog+u...@clarkparsia.com

Bart van Leeuwen

unread,

Nov 15, 2016, 8:41:06 AM11/15/16

to Stardog

This is directly related to my other post on a Jena dependencies update

A update to Jena 3.0.1 would solve this issue, although a wider upgrade to 3.1.1 would even better.

https://groups.google.com/a/clarkparsia.com/forum/#!topic/stardog/YtXSzQl-XFg

Op maandag 14 november 2016 14:01:29 UTC+1 schreef Bart van Leeuwen:

Reply all

Reply to author

Forward