You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@jena.apache.org by Bart van Leeuwen <ba...@netage.nl> on 2015/04/12 20:32:37 UTC

Fuseki2 Documentation

Hi,

I've been playing around with the new Fuseki2 WAR option.
I love the fact that I can include it through maven in a TOMEE build.

What does puzzle me is the configuration, there is a mention of a dataset 
file in the /configaration/ directory.
but when I put the files there i just get errors:
[2015-04-12 20:30:57] Server     ERROR Exception in initialization: Not 
found: firebrary.ttl

Then there are some links which lead nowhere, I wouldn't mind helping out 
if someone would explain me the details how it works.

Met Vriendelijke Groet / With Kind Regards
Bart van Leeuwen

##############################################################
# twitter: @semanticfire
# netage.nl
# http://netage.nl
# M.A. Reinaldaweg 79
# 3461AJ Linschoten
# tel. +31(0)6-53182997
##############################################################

Re: Fuseki2 Documentation

Posted by Andy Seaborne <an...@apache.org>.
On 12/04/15 19:32, Bart van Leeuwen wrote:
> Hi,
>
> I've been playing around with the new Fuseki2 WAR option.
> I love the fact that I can include it through maven in a TOMEE build.
>
> What does puzzle me is the configuration, there is a mention of a dataset
> file in the /configaration/ directory.
> but when I put the files there i just get errors:
> [2015-04-12 20:30:57] Server     ERROR Exception in initialization: Not
> found: firebrary.ttl

Looks like an issue in resolving relative URIs.  What's the 
configuration file look like?

>
> Then there are some links which lead nowhere, I wouldn't mind helping out
> if someone would explain me the details how it works.

There is some more on jena.staging.apache.org.

The website is in

https://svn.apache.org/repos/asf/jena/site/trunk/

(yes - SVN)

and the content in markdown.

You can also propose changes via your browser with the "improve this 
page" button which takes you into the online CMS editor.  That then 
sends a proposed commit to the project.

That's good for small changes - for large changes, editing the svn and 
sending a patch is easier to do.

	Andy

>
> Met Vriendelijke Groet / With Kind Regards
> Bart van Leeuwen
>
> ##############################################################
> # twitter: @semanticfire
> # netage.nl
> # http://netage.nl
> # M.A. Reinaldaweg 79
> # 3461AJ Linschoten
> # tel. +31(0)6-53182997
> ##############################################################
>