Author: buildbot
Date: Fri Aug 30 16:03:52 2013
New Revision: 876728
Log:
Staging update by buildbot for jena
Modified:
websites/staging/jena/trunk/content/ (props changed)
websites/staging/jena/trunk/content/documentation/query/http-auth.html
Propchange: websites/staging/jena/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Fri Aug 30 16:03:52 2013
@@ -1 +1 @@
-1518998
+1519009
Modified: websites/staging/jena/trunk/content/documentation/query/http-auth.html
==============================================================================
--- websites/staging/jena/trunk/content/documentation/query/http-auth.html
(original)
+++ websites/staging/jena/trunk/content/documentation/query/http-auth.html Fri
Aug 30 16:03:52 2013
@@ -119,7 +119,7 @@ credentials will not actually be submitt
as appropriate. Similarly to the simple authenticator this is not preemptive
authentication so credentials are not sent unless the service requests them.</p>
<p>Scoping of credentials is not based on exact mapping of the request URI to
credentials but rather on a longest match approach. For example if you define
credentials
for <code>http://example.org</code> then these are used for any request that
requires authentication under that URI e.g.
<code>http://example.org/some/path</code>. However if you
-had defined credentials for <code>http://example.org/some/path</code> then
these would be used in favor of those for <code>http://example.org</code></p>
+had also defined credentials for <code>http://example.org/some/path</code>
then these would be used in favor of those for
<code>http://example.org</code></p>
<h4 id="serviceauthenticator">ServiceAuthenticator</h4>
<p>The <a
href="http://jena.apache.org/documentation/javadoc/arq/org/apache/jena/atlas/web/auth/ServiceAuthenticator.html";>service
authenticator</a> is an authenticator which uses information encoded in the
ARQ context and basically provides access to the existing credential provision
mechanisms provided for the <code>SERVICE</code> clause, see <a
href="service.html">Basic Federated Query</a> for more information on
configuration for this.</p>
@@ -145,7 +145,7 @@ that allows you to configure an arbitrar
<li><a
href="http://jena.apache.org/documentation/javadoc/arq/com/hp/hpl/jena/sparql/modify/UpdateProcessRemoteBase.html";>UpdateProcessRemoteBase</a>
- This is the base class of <code>UpdateProcessor</code> implementations
returned by <code>UpdateExecutionFactory.createRemote()</code> and
<code>UpdateExecutionFactory.createRemoteForm()</code> calls</li>
<li><a
href="http://jena.apache.org/documentation/javadoc/arq/org/apache/jena/web/DatasetGraphAccessorHTTP.html";>DatasetGraphAccessorHTTP</a>
- This is the <code>DatasetGraphAccessor</code> implementation underlying
remote dataset accessors.</li>
</ul>
-<p>From 2.10.2 onwards the relevant factory methods include overloads that
allow providing a <code>HttpAuthenticator</code> at creation time which
+<p>From 2.11.0 onwards the relevant factory methods include overloads that
allow providing a <code>HttpAuthenticator</code> at creation time which
avoids the needs to cast and manually set the authenticator afterwards.</p>
<h3 id="the-default-authenticator">The Default Authenticator</h3>
<p>Since it may not always be possible/practical to configure authenticators
on a per-request basis the API includes a means to specify a default
authenticator
