Author: sallen
Date: Wed Aug 5 23:08:26 2015
New Revision: 1694345
URL: http://svn.apache.org/r1694345
Log:
Remove non-Jena related discussion from the documentation and javadocs.
Modified:
jena/Experimental/jena-client/jena-client.mdtext
jena/Experimental/jena-client/src/main/java/org/apache/jena/client/Connection.java
jena/Experimental/jena-client/src/main/java/org/apache/jena/client/DatabaseClientFactory.java
Modified: jena/Experimental/jena-client/jena-client.mdtext
URL:
http://svn.apache.org/viewvc/jena/Experimental/jena-client/jena-client.mdtext?rev=1694345&r1=1694344&r2=1694345&view=diff
==============================================================================
--- jena/Experimental/jena-client/jena-client.mdtext (original)
+++ jena/Experimental/jena-client/jena-client.mdtext Wed Aug 5 23:08:26 2015
@@ -103,26 +103,7 @@ This will ensure that `close()` is calle
Remote databases are treated the same as local databases with the following
exception: there is no remote transaction support yet. There is no W3C
standard for
remote SPARQL transactions, so this needs to be designed and implemented in
Fuseki before jena-client can add support.
-**Note:** Databases other than Jena Fuseki may be severely limited on the type
and size of remote SPARQL 1.1 Update requests. For example,
[Sesame](http://rdf4j.org/)
-(and Sesame-derived databases) have two main limitations:
-
-* Sesame only supports the `application/x-www-form-urlencoded` content-type.
By default `HttpDatabaseClient` will use
- the `application/sparql-update` content-type, but it can be changed to use
`application/x-www-form-urlencoded` by setting
- the appropriate type with `setUpdateContentType()` method. However, be
aware that when `application/x-www-form-urlencoded` is used
- then the update will not be streaming and will be buffered entirely into
memory before being submitted to the server.
-
- HttpDatabaseClient client =
DatabaseClientFactory.createRemote(queryEndpoint, updateEndpoint);
- client.setUpdateContentType(WebContent.contentTypeHTMLForm);
-
-
-* Sesame parses SPARQL update requests into an in-memory Abstract Syntax Tree
(AST) completely before executing the query. This can cause two issues:
- 1) an update request with a large number of operations may cause a an
OutOfMemoryException; and 2) INSERT DATA and DELETE DATA operations are not
- streamed into the underlying repository, and large such operations may cause
either an OutOfMemoryException or a StackOverflowException.
- The work-around for this issue is to break your update query into smaller
chunks and submit them as separate update requests.
- **Note:** Sesame may not actually report the true exception, rather it seems
to
- report `org.openrdf.http.server.ClientHTTPException: Unsupported MIME type:
application/x-www-form-urlencoded` when
- a large update request is submitted.
-
+**Note:** Databases other than Jena Fuseki may be limited on the type and size
of remote SPARQL 1.1 Update requests.
## Authentication
Modified:
jena/Experimental/jena-client/src/main/java/org/apache/jena/client/Connection.java
URL:
http://svn.apache.org/viewvc/jena/Experimental/jena-client/src/main/java/org/apache/jena/client/Connection.java?rev=1694345&r1=1694344&r2=1694345&view=diff
==============================================================================
---
jena/Experimental/jena-client/src/main/java/org/apache/jena/client/Connection.java
(original)
+++
jena/Experimental/jena-client/src/main/java/org/apache/jena/client/Connection.java
Wed Aug 5 23:08:26 2015
@@ -129,7 +129,7 @@ public interface Connection extends Tran
* large updates that would not otherwise fit into memory. It also allows
streaming
* RDF files and Models to the database as well.
*
- * @param action an {@link Action} that will apply updates to a suppled
{@link Updater} object;
+ * @param action an {@link Consumer} that will apply updates to a suppled
{@link Updater} object;
* these updates are streamed into the database
* @return an UpdateStatement based on the supplied <code>{@literal
Action<Updater>}</code>
*/
Modified:
jena/Experimental/jena-client/src/main/java/org/apache/jena/client/DatabaseClientFactory.java
URL:
http://svn.apache.org/viewvc/jena/Experimental/jena-client/src/main/java/org/apache/jena/client/DatabaseClientFactory.java?rev=1694345&r1=1694344&r2=1694345&view=diff
==============================================================================
---
jena/Experimental/jena-client/src/main/java/org/apache/jena/client/DatabaseClientFactory.java
(original)
+++
jena/Experimental/jena-client/src/main/java/org/apache/jena/client/DatabaseClientFactory.java
Wed Aug 5 23:08:26 2015
@@ -57,35 +57,7 @@ public class DatabaseClientFactory
/**
* Creates a database client around a remote SPARQL HTTP-compliant
database with no authentication.
* <p>
- * <strong>Note:</strong> Databases other than Jena Fuseki may be severely
limited on the type and size
- * of SPARQL 1.1 Update queries. For example, Sesame (and Sesame-based
endpoints) have two main limitations:
- * <ol>
- * <li>
- * Sesame only supports the {@code
"application/x-www-form-urlencoded"} content-type. By default DatabaseClient
- * will use the {@code "application/sparql-update"} content-type, but
it can be changed to use
- * {@code "application/x-www-form-urlencoded"} by setting the
appropriate type on the {@link HttpDatabaseClient} object.
- * <code>
- * <pre>
- * HttpDatabaseClient client =
DatabaseClientFactory.createRemote(queryEndpoint, updateEndpoint);
- * client.setUpdateContentType(WebContent.contentTypeHTMLForm);</pre>
- * </code>
- * <strong>Warning:</strong> When
<code>"application/x-www-form-urlencoded"</code> is used then the update
request will not be
- * streaming and will be buffered entirely into memory before being
submitted to the server.
- * </li>
- * <p><br>
- * <li>
- * Sesame parses SPARQL Update request into an in-memory Abstract
Syntax Tree (AST) completely before executing the
- * query. This can cause two issues: 1) an update request with a
large number of operations may cause a an OutOfMemoryException;
- * and 2) INSERT DATA and DELETE DATA operations are not streamed into
the underlying repository, and large such operations
- * may cause either an OutOfMemoryException or a
StackOverflowException.
- * <p><br>
- * <strong>Note:</strong> Sesame may not actually report the true
exception, rather it seems to report
- * {@code org.openrdf.http.server.ClientHTTPException: Unsupported
MIME type: application/x-www-form-urlencoded} when
- * a large update requst is submitted.
- * <p><br>
- * The work-around for this issue is to break your update query into
smaller chunks and submit them as separate update requests.
- * </li>
- * </ol>
+ * <strong>Note:</strong> Databases other than Jena Fuseki may be limited
on the type and size of SPARQL 1.1 Update queries.
*
* @param queryEndpoint the SPARQL query endpoint URL; if null, then you
may not execute queries against the endpoint
* @param updateEndpoint the SPARQL update endpoint URL; if null, then you
may not execute updates against the endpoint
@@ -99,35 +71,6 @@ public class DatabaseClientFactory
/**
* Creates a database client around a remote SPARQL HTTP-compliant
database.
* <p>
- * <strong>Note:</strong> Databases other than Jena Fuseki may be severely
limited on the type and size
- * of SPARQL 1.1 Update queries. For example, Sesame (and Sesame-based
endpoints) have two main limitations:
- * <ol>
- * <li>
- * Sesame only supports the {@code
"application/x-www-form-urlencoded"} content-type. By default DatabaseClient
- * will use the {@code "application/sparql-update"} content-type, but
it can be changed to use
- * {@code "application/x-www-form-urlencoded"} by setting the
appropriate type on the {@link HttpDatabaseClient} object.
- * <code>
- * <pre>
- * HttpDatabaseClient client =
DatabaseClientFactory.createRemote(queryEndpoint, updateEndpoint);
- * client.setUpdateContentType(WebContent.contentTypeHTMLForm);</pre>
- * </code>
- * <strong>Warning:</strong> When
<code>"application/x-www-form-urlencoded"</code> is used then the update
request will not be
- * streaming and will be buffered entirely into memory before being
submitted to the server.
- * </li>
- * <p><br>
- * <li>
- * Sesame parses SPARQL Update request into an in-memory Abstract
Syntax Tree (AST) completely before executing the
- * query. This can cause two issues: 1) an update request with a
large number of operations may cause a an OutOfMemoryException;
- * and 2) INSERT DATA and DELETE DATA operations are not streamed into
the underlying repository, and large such operations
- * may cause either an OutOfMemoryException or a
StackOverflowException.
- * <p><br>
- * <strong>Note:</strong> Sesame may not actually report the true
exception, rather it seems to report
- * {@code org.openrdf.http.server.ClientHTTPException: Unsupported
MIME type: application/x-www-form-urlencoded} when
- * a large update requst is submitted.
- * <p><br>
- * The work-around for this issue is to break your update query into
smaller chunks and submit them as separate update requests.
- * </li>
- * </ol>
*
* @param queryEndpoint the SPARQL query endpoint URL; if null, then you
may not execute queries against the endpoint
* @param updateEndpoint the SPARQL update endpoint URL; if null, then you
may not execute updates against the endpoint
