Strolch
/
strolch
mirror of https://github.com/strolch-li/strolch.git
1
1
Fork 0
Code Issues Packages Projects Releases Wiki Activity

[Project] Removed mention of transactional from website

This commit is contained in:
Robert von Burg 2018-02-27 18:47:12 +01:00
parent 09469a2b45
commit 5618e0e893
2 changed files with 7 additions and 22 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
li.strolch.website/www.strolch.li/api.html
View File

@ -210,10 +210,6 @@ try (StrolchTransaction tx = openTx(realmName)) {
<p>In this mode, all data is stored in memory, and any changes made are written back to the persistence
layer. This allows for fast in-memory quries, but makes sure no data is lost when the agent is
restarted.</p></li>
<li>TRANSACTIONAL
<p>In this mode no data is kept in memory and every query, and root element retrieval is passed to the
persistence layer to be retrieved from the underlying database. This is what comes closest to a
typical Java+Hibernate implementation.</p></li>
</ul>
<p>Strolch Realms are also responsible for opening Transactions, as these are bound to the persistence layer
@ -404,8 +400,7 @@ public class SetParameterCommand extends Command {
</li>
<li>Configure and maintain the realms, which implement the multi-client capability</li>
<li>Provide a default ServiceHandler to perform Services at runtime</li>
<li>Implements the realms which each can operate in different modes data store modes: TRANSACTIONAL,
CACHED, TRANSIENT
<li>Implements the realms which each can operate in different modes data store modes: CACHED, TRANSIENT
</li>
</ul>
</li>
@ -425,12 +420,12 @@ public class SetParameterCommand extends Command {
<li><a href="https://github.com/4treesCH/strolch/tree/master/li.strolch.persistence.postgresql">li.strolch.persistence.postgresql</a>
<p>Implements a PostgreSQL persistence layer so that the Strolch model can be persisted to a PostgreSQL
RDBMS when the realm is configured to have a data store mode of either CACHED or TRANSACTIONAL</p>
RDBMS when the realm is configured to have a data store mode of CACHED.</p>
</li>
<li><a href="https://github.com/4treesCH/strolch/tree/master/li.strolch.persistence.xml">li.strolch.persistence.xml</a>
<p>Implements an XML persistence layer so that the Strolch model can be persisted to XML files when the
realm is configured to have a data store mode of either CACHED or TRANSACTIONAL.</p>
realm is configured to have a data store mode of CACHED.</p>
</li>
<li><a href="https://github.com/4treesCH/strolch/tree/master/li.strolch.rest">li.strolch.rest</a>

18
li.strolch.website/www.strolch.li/documentation-realms.html
View File

@ -68,10 +68,6 @@
persistence layer. This allows for fast in-memory qeuries, but makes sure no data is lost when the agent
is restarted.
</li>
<li>TRANSACTIONAL <br/> In this mode no data is kept in-memory and every query, and element retrieval is
passed to the persistence layer to be retrieved from the underlying database. This is similar to typical
Java applications where JPA is used.
</li>
</ul>
<p>Realms are mostly hidden from a developer as a <code>StrolchTransaction</code> exposes all important
@ -79,7 +75,7 @@
specific project. If the project only requires one realm, then the <code>defaultRealm</code> can be used,
where the developer only is required to configure the mode and any relevant model file.</p>
<p>If the mode is CACHED or TRANSACTIONAL, then the <code>PersistenceHandler</code> component is required to be
<p>If the mode is CACHED, then the <code>PersistenceHandler</code> component is required to be
configured, so that the DAOs know how to access the underlying database.</p>
<p>The configuration in the <code>StrolchConfiguration.xml</code> file is as follows:</p>
@ -93,10 +89,10 @@
&lt;api&gt;li.strolch.agent.api.RealmHandler&lt;/api&gt;
&lt;impl&gt;li.strolch.agent.impl.DefaultRealmHandler&lt;/impl&gt;
&lt;depends&gt;PrivilegeHandler&lt;/depends&gt;
&lt;!-- if CACHED or TRANSACTIONAL: --&gt;
&lt;!-- if CACHED: --&gt;
&lt;!--depends&gt;PersistenceHandler&lt;/depends--&gt;
&lt;Properties&gt;
&lt;dataStoreMode&gt;EMPTY|TRANSIENT|CACHED|TRANSACTIONAL&lt;/dataStoreMode&gt;
&lt;dataStoreMode&gt;EMPTY|TRANSIENT|CACHED&lt;/dataStoreMode&gt;
&lt;dataStoreFile&gt;StrolchModel.xml&lt;/dataStoreFile&gt;
&lt;/Properties&gt;
&lt;/Component&gt;
@ -120,10 +116,9 @@
&lt;depends&gt;PrivilegeHandler&lt;/depends&gt;
&lt;depends&gt;PersistenceHandler&lt;/depends&gt;
&lt;Properties&gt;
&lt;realms&gt;defaultRealm, cachedRealm, transactionalRealm&lt;/realms&gt;
&lt;realms&gt;defaultRealm, cachedRealm&lt;/realms&gt;
&lt;dataStoreMode&gt;TRANSIENT&lt;/dataStoreMode&gt;
&lt;dataStoreFile&gt;DefaultRealm.xml&lt;/dataStoreFile&gt;
&lt;dataStoreMode.transactionalRealm&gt;TRANSACTIONAL&lt;/dataStoreMode.transactionalRealm&gt;
&lt;dataStoreMode.cachedRealm&gt;CACHED&lt;/dataStoreMode.cachedRealm&gt;
&lt;dataStoreMode.emptyRealm&gt;EMPTY&lt;/dataStoreMode.emptyRealm&gt;
&lt;/Properties&gt;
@ -137,11 +132,6 @@
&lt;allowSchemaCreation&gt;true&lt;/allowSchemaCreation&gt;
&lt;allowSchemaDrop&gt;true&lt;/allowSchemaDrop&gt;
&lt;db.url.transactionalRealm&gt;jdbc:postgresql://localhost/testdb1&lt;/db.url.transactionalRealm&gt;
&lt;db.username.transactionalRealm&gt;testuser1&lt;/db.username.transactionalRealm&gt;
&lt;db.password.transactionalRealm&gt;test&lt;/db.password.transactionalRealm&gt;
&lt;db.pool.maximumPoolSize.transactionalRealm&gt;1&lt;/db.pool.maximumPoolSize.transactionalRealm&gt;
&lt;db.url.cachedRealm&gt;jdbc:postgresql://localhost/testdb2&lt;/db.url.cachedRealm&gt;
&lt;db.username.cachedRealm&gt;testuser2&lt;/db.username.cachedRealm&gt;
&lt;db.password.cachedRealm&gt;test&lt;/db.password.cachedRealm&gt;