You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@polygene.apache.org by ni...@apache.org on 2017/10/30 07:03:30 UTC
polygene-java git commit: Fixing javadoc error
Repository: polygene-java
Updated Branches:
refs/heads/develop 1d75d91e4 -> 6eaa8d47b
Fixing javadoc error
Project: http://git-wip-us.apache.org/repos/asf/polygene-java/repo
Commit: http://git-wip-us.apache.org/repos/asf/polygene-java/commit/6eaa8d47
Tree: http://git-wip-us.apache.org/repos/asf/polygene-java/tree/6eaa8d47
Diff: http://git-wip-us.apache.org/repos/asf/polygene-java/diff/6eaa8d47
Branch: refs/heads/develop
Commit: 6eaa8d47b44f1791e1e0e8f0419558c256dcffc8
Parents: 1d75d91
Author: niclas <ni...@hedhman.org>
Authored: Mon Oct 30 15:03:24 2017 +0800
Committer: niclas <ni...@hedhman.org>
Committed: Mon Oct 30 15:03:24 2017 +0800
----------------------------------------------------------------------
.../berkeleydb/BerkeleyDBEntityStoreConfiguration.java | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/polygene-java/blob/6eaa8d47/extensions/entitystore-berkeleydb/src/main/java/org/apache/polygene/entitystore/berkeleydb/BerkeleyDBEntityStoreConfiguration.java
----------------------------------------------------------------------
diff --git a/extensions/entitystore-berkeleydb/src/main/java/org/apache/polygene/entitystore/berkeleydb/BerkeleyDBEntityStoreConfiguration.java b/extensions/entitystore-berkeleydb/src/main/java/org/apache/polygene/entitystore/berkeleydb/BerkeleyDBEntityStoreConfiguration.java
index 0701e5c..1acb557 100644
--- a/extensions/entitystore-berkeleydb/src/main/java/org/apache/polygene/entitystore/berkeleydb/BerkeleyDBEntityStoreConfiguration.java
+++ b/extensions/entitystore-berkeleydb/src/main/java/org/apache/polygene/entitystore/berkeleydb/BerkeleyDBEntityStoreConfiguration.java
@@ -287,6 +287,7 @@ public interface BerkeleyDBEntityStoreConfiguration
* data structure. Btree objects are not serialized the main cache, so no object materialization is needed to
* access the Btree there. Access to records in the main cache is therefore very fast, but the main cache has
* drawbacks as well:
+ * </p>
* <ol>
* <li>
* The larger the main cache, the more likely it is to have Java GC performance problems.
@@ -298,9 +299,9 @@ public interface BerkeleyDBEntityStoreConfiguration
* cache.
* </li>
* </ol>
- * </p>
* <p>
* The use of the file system cache has performance benefits, but also has its own drawbacks:
+ * </p>
* <ol>
* <li>
* There is a significant redundancy between the main cache and the file system cache because all data and Btree
@@ -312,7 +313,6 @@ public interface BerkeleyDBEntityStoreConfiguration
* words, the size of the main cache alone determines the maximum size of the in-memory "dirty set".
* </li>
* </ol>
- * </p>
* <p>
* The off-heap cache is stored outside the Java heap using a native platform memory allocator. The current
* implementation relies on internals that are specific to the Oracle and IBM JDKs; however, a memory allocator