On 07/08/13 16:03, Howard Burrows wrote:
I would like to define (assemble) my various Fuseki "Services" in separate files and then
import them into a master assembler file and reference them in the services list of the Fuseki
"Server" definition.
However, no matter how I define it I always get a "org.apache.jena.fuseki.FusekiConfigException:
No name for service <<service_name>>" for my imported service. I'm able to
successfully use imported definitions (via ja:imports) for other purposes (i.e. like defining a
common tdb:DatasetTDB) but not for defining a Fuseki service. I suspect I just don't understand the
semantics of the ja:imports construct or maybe have something wrong... but my ja:imports work for
some things and not others.
Should I be able to do this? Any suggestions on best practices, etc.?
Thanks,
Howard Burrows
ja:imports is for working with owl:imports. There's no special
#includes mechanism. You could cat appropriate files to dynamically
build the config and put a wrapper about the start up Fuseki script.
Andy
