# Stardog 4.2.3 and Sesame (RDF4J)

**URL:** <https://community.stardog.com/t/stardog-4-2-3-and-sesame-rdf4j/109>\
**Category:** Support\
**Created:** [February 14, 2017, 1:37pm UTC](https://community.stardog.com/t/stardog-4-2-3-and-sesame-rdf4j/109 "2017-02-14T13:37:20Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![FabianCretton](https://avatars.discourse-cdn.com/v4/letter/f/edb3f5/32.png) [@FabianCretton](https://community.stardog.com/u/FabianCretton)\
**Post date:** [February 14, 2017, 1:37pm UTC](https://community.stardog.com/t/stardog-4-2-3-and-sesame-rdf4j/109/1 "2017-02-14T13:37:20Z")

</div>

Hi,

I am trying to interact with Stardog 4.2.3 from java code. I had a look at a few resources from [https://docs.stardog.com](https://docs.stardog.com) (about using sesame, maven) as well as the code example from github.

My goal was to integrate the Stardog access in an existing project that relies on RDF4J and thus Java 8.  
From the Maven configuration proposed here above, it seems that the current code was not ported yet to RDF4J but still relies on older Sesame libraries, which does cause conflicts in my current project.

My solution so far was to not use the _StardogRepository_ connection, but interact with Stardog through the SPARQL end-point, using the RDF4J _SPARQLRepository_ class. This works fine but doesn't give the same functionalities as a _RepositoryConnection_.

**My questions are:**

- is it feasible to to do something similar to [Example of how to use Stardog's Sesame bindings · GitHub](https://gist.github.com/mhgrove/1045568) with RDF4J, if so, is there any example ?
- is it correct that the StardogRepository class is needed here, and Stardog can not be accessed through the standard RemoteRepositoryManager from RDF4J (and Sesame too)

Thank you for any help  
Fabian

---

<div class="post-metadata">

**Author:** ![mike](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.stardog.com/mike/32/14_2.png) [@mike](https://community.stardog.com/u/mike)\
**Post date:** [February 17, 2017, 1:24pm UTC](https://community.stardog.com/t/stardog-4-2-3-and-sesame-rdf4j/109/2 "2017-02-17T13:24:24Z")

</div>

1. Yes it would be easy to replicate what we’ve done with the Sesame bindings, but for RDF4j, it’s probably only an afternoon to build the appropriate wrappers around the core Stardog APIs.

2. Correct, the `RemoteRepositoryManager` is not usable with Stardog, it’s _very_ tightly coupled to Sesame/RDF4j and is only compatible with their `HTTPRepository` implementation. This is a known issue for them.

Cheers,

Mike

---

<div class="post-metadata">

**Author:** ![system](https://canada1.discourse-cdn.com/flex030/uploads/stardog/original/2X/e/ed66b48a616f505106a4acde3c9cee7e6da9bc67.svg) [@system](https://community.stardog.com/u/system)\
**Post date:** [March 3, 2017, 1:24pm UTC](https://community.stardog.com/t/stardog-4-2-3-and-sesame-rdf4j/109/3 "2017-03-03T13:24:57Z")

</div>

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.