Author: buildbot
Date: Fri Apr 5 21:04:00 2019
New Revision: 1043256
Log:
Staging update by buildbot for jena
Modified:
websites/staging/jena/trunk/content/ (props changed)
websites/staging/jena/trunk/content/documentation/fuseki2/fuseki-main.html
Propchange: websites/staging/jena/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Fri Apr 5 21:04:00 2019
@@ -1 +1 @@
-1856962
+1857034
Modified:
websites/staging/jena/trunk/content/documentation/fuseki2/fuseki-main.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/fuseki2/fuseki-main.html
(original)
+++ websites/staging/jena/trunk/content/documentation/fuseki2/fuseki-main.html
Fri Apr 5 21:04:00 2019
@@ -160,11 +160,11 @@
visibility: hidden;
}
h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink,
h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink,
dt:hover > .elementid-permalink { visibility: visible }</style>
-<p>Fuseki main is a packaging of Fuseki as trile store without a UI for
administration.</p>
+<p>Fuseki main is a packaging of Fuseki as a triple store without a UI for
administration.</p>
<p>Fuseki can be run in the background by an application as an embedded
server. The
application can safely work with the dataset directly from java while having
Fuseki
provide SPARQL access over HTTP. An embedded server is useful for
-adding functonality around a triple store and also for development and
testing.</p>
+adding functionality around a triple store and also for development and
testing.</p>
<ul>
<li><a href="#fuseki-server">Running as a deployment or development
server</a></li>
<li><a href="#usage">Application Use</a></li>
@@ -188,7 +188,7 @@ persistent work area on-disk.</p>
<p>The arguments are the same as the
<a
href="http://jena.apache.org/documentation/fuseki2/fuseki-run.html#fuseki-standalone-server";>full
UI server command line
program</a>.
-There are no special enviornment variables.</p>
+There are no special environment variables.</p>
<p>The entry point is
<code>org.apache.jena.fuseki.main.cmds.FusekiMainCmd</code> so
the server can also be run as:</p>
<div class="codehilite"><pre><span class="n">java</span> <span
class="o">-</span><span class="n">cp</span> <span class="n">jena</span><span
class="o">-</span><span class="n">fuseki</span><span class="o">-</span><span
class="n">server</span><span class="o">-</span>$<span class="n">VER</span><span
class="p">.</span><span class="n">jar</span><span class="p">:...</span><span
class="n">OtherJars</span><span class="p">...</span> <span class="o">\</span>
@@ -248,7 +248,7 @@ is quite large and difficult to set manu
<p>This dependency does not include a logging setting. Fuseki uses <a
href="http://slf4j.org/";>slf4j</a>.
See section "<a href="#logging">Logging</a>" for details.</p>
<p>If the application wishes to use a dataset with a <a
href="http://jena.apache.org/documentation/query/text-query.html";>text-index</a>
-then the application wil also need to include jena-text in its
dependencies.</p>
+then the application will also need to include jena-text in its
dependencies.</p>
<h2 id="logging">Logging<a class="headerlink" href="#logging" title="Permanent
link">¶</a></h2>
<p>The application must set the logging provided for <a
href="http://slf4j.org/";>slf4j</a>.
Apache jena provides helpers for the JDK-provided java logging and for Apache
Log4j v1.</p>
