Folks I've been looking at the feasibility of adopting the Fuseki 2 UI as a front end for a work project. Historically we used Fuseki 1 once upon a time but at the time it was very difficult to extend and we eventually abandoned it in favour of a in-house solution. With the Fuseki 2 implementation now relatively mature we are considering moving back to Fuseki to reduce the amount of wheel reinvention we need to do.
>From a practical standpoint what I am looking at doing is creating an artifact similar to jena-fuseki-server that pulls in jena-fuseki-core and embeds Jetty as the application server. One stumbling block is that I want to start from the default webapp that Fuseki 2 provides and possibly customise it which as it stands means I'd need to unpack jena-fuseki-war.war or the binary distribution to get the webapp directory. It would seem fairly trivial to introduce another artifact that is simply a maven assembly packaging of the web app source that others can then more easily consume so I will do this probably today. This will also be an exercise in how easy it is to configure and drive a Fuseki server instance through the programmatic API so I may have be making some minor API changes or starting discussions as needed Rob
