We actually reference it as a library (via maven) and call Fuseki.init() in our startup code to actually start up Fuseki.
We then have our own init() routine which registers all the relevant query engines and does other setup - custom describe handler, optimization config etc Even if we were using 0.2.1 I think we would prefer not to use assembler descriptions as that would allow users to break things by changing the file. Also we configure differently depending on the command line arguments our code received and I don't know that assembler would allow us to cope with that nicely (though I think we can call arbitrary code?) Rob On Jan 12, 2012, at 11:48 AM, Andy Seaborne wrote: > On 12/01/12 17:31, Robert Vesse wrote: >> We use it as a library quite heavily! > > Oops - I didn't know anyone even could do that! Sorry. > > How do you use it? Are you using the servlets and your own configuration > setting? > > 0.2.1 introduces a config file where you can put assembler descriptions. > > Andy > > >> >> We're still using pre-Apache Fuseki 0.2.0 for the time being so this >> shouldn't affect us just yet. >> >> Rob >> ________________________________________ >> From: Andy Seaborne [[email protected]] >> Sent: 12 January 2012 01:20 >> To: [email protected] >> Subject: Fuseki repackage >> >> I changed the package structure for Fuseki to be org.apache.jena.fuseki. >> No one uses it as a library (except me) so the change should be >> transparent - the server jar executes from the built-in main class set >> via the POM. >> >> Andy >
