Given how old the D2R dependencies are I suspect you would need to take the source of D2R and upgrade it manually to the latest Jena versions.
Trying to mix and match dependencies like this (particularly across the transition to Apache) is just going to lead to class path hell due to all the refactoring and improvements that have happened in Jena since then. Rob On 7/5/13 7:19 AM, "Alex Lee" <[email protected]> wrote: >Hi, > >I am trying to get a Fuseki server to interface with D2R Update as its >data >source. My initial attempts have involved including the D2R packages in >the >fuseki-server.jar and running the server with a simple D2R assembler >config >file. Through this method, I've gotten as far as getting the server to >start-up with a data source, but have been unsuccessful in getting any >queries to work. As errors have been coming up, I've simply added or >removed any classes that have been causing problems, but this has been >very >slow and brute-forced. I'm hoping there is a better solution that >preferably doesn't involve modifying source code. > >The root of the issue seems to lie in the fact D2R Update uses Jena 2.6.3 >and Jena ARQ 2.8.5, while the oldest version of Fuseki uses Jena 2.7.0 and >Jena ARQ 2.9.0. Based on the javadocs for each of these packages, it seems >there has been significant changes in their structures between versions, >such that D2R doesn't play nice with newer Jena/ARQ, and vice versa for >Fuseki with older Jena/ARQ. > >My question is: Has anyone been able to successfully implement this setup? >Is it even possible to get this to work with just modifying various >run-time configurations, or is direct modification and re-compilation of >the code necessary? > >Thanks, > >-- >Alex
