Andy, Thanks for following up. I decided that our code is too wired into Joseki to move to Fuseki at this time. This wasn’t due to any one single issue, but rather the multiplicity of issues I was facing. I’m not sure how I’m going to deal with this, since for now this decision limits me to a fairly old version of Jena+Arq (2.7.4+2.9.4, to be specific). I’m either going to have to take the last version of Joseki source and port it forward to modern Jena, or I’m going to have to figure out how to make Parliament work with Fuseki, which will require some major surgery (to both Parliament and Fuseki).
Thanks, Ian On Apr 19, 2014, at 12:06 PM, Andy Seaborne <[email protected]> wrote: > Ian - did this get sorted out? > > Andy > > On 20/03/14 15:07, Andy Seaborne wrote: >> On 20/03/14 14:10, Ian Emmons wrote: >>> I am working with Fuseki 2, as checked out from here: >>> >>> https://svn.apache.org/repos/asf/jena/branches/jena-fuseki-new-ui >>> >>> It is not recognizing the config file that I pass in with the >>> --config= command line argument. In tracing through the code, I see >>> that FusekiCmd parses this parameter correctly, stashes it in a member >>> called cmdLineDataset, and then sets this onto the >>> FusekiServletContextListener class's static member initialSetup. >>> Then, FusekiServletContextListener.init() passes initialSetup to >>> FusekiServer.initializeDataAccessPoints(), which initiates the whole >>> assembler thing. The problem appears to be that >>> FusekiServletContextListener.init() is never called. In fact, I can't >>> find a single place in the whole Fuseki code base where this class is >>> instantiated. >>> >>> What am I missing? How is this supposed to work? >>> >>> Thanks, >>> >>> Ian >> >> >> It's called because it is a ServletContextListener and it's named in >> web.xml as a <listener>. >> >> Andy >> >> PS The general idea is that assembler files go in "configuration/" one >> data service per file. Fuseki 1 style --config will still be supported.
