Hi, I write down some notes even if I don't see much progress... I followed the stack trace step by step looking at bundles that provide the packages (from the Felix Packages tool), here is the sequence:
org.apache.commons.logging.impl.SLF4JLogFactory => org.slf4j:jcl.over.slf4j 1.6.6 org.apache.http => org.apache.httpcomponents:httpcore-nio org.apache.jena => org.apache.clerezza.ext:org.apache.jena.tdb com.hp.hpl.jena => org.apache.clerezza.ext:org.apache.jena.tdb org.apache.stanbol.reasoners.web => I know this... then org.apache.stanbol.reasoners.web when there is the code I know that is calling a method from Jena to load a resource from http. But this only shows where packages should be kept from, not which is actually the origin of the ones loaded in the current classpath, that deal to the exception. I also noticed that has a set of jars embedded in the classpath, including jcl-over-slf4j-1.6.4.jar , but this is not exported so I can't see how it should affect my classpath. I am stuck here, for the moment. Enrico On 19 November 2013 20:59, enridaga <enrid...@apache.org> wrote: > Hi Reto, > > > On 19 November 2013 20:50, Reto Bachmann-Gmür <r...@wymiwyg.com> wrote: > >> Hi, >> >> >> FWIW, it looks like we have two options here: >> >>> 1) Upgrade jena to 2.11.0 . This would be something to do at some point. >>> Unfortunately this implies switch the dependencies to the org.apache.* >>> one. >>> Package names should be the same - not 100% sure. >>> >> In Clerezza the switch was quite painless. Also in fusepool we are using >> jena 2.11 and tdb 1.0 and had no issues with the Stanbol components used. >> > This is promising. I would fix the problem with the Reasoners services > first, then we may want to discuss the upgrade of Jena, of course. > > Enrico > > >> Cheers, >> Reto >> > > > > -- > > ------------------------------------------------------------------------------ > enridaga > -- ------------------------------------------------------------------------------ enridaga
