You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@sling.apache.org by ss...@apache.org on 2014/10/14 11:31:13 UTC
svn commit: r1631696 -
/sling/site/trunk/content/documentation/development/sling-mock.mdtext
Author: sseifert
Date: Tue Oct 14 09:31:12 2014
New Revision: 1631696
URL: http://svn.apache.org/r1631696
Log:
update formatting
Modified:
sling/site/trunk/content/documentation/development/sling-mock.mdtext
Modified: sling/site/trunk/content/documentation/development/sling-mock.mdtext
URL: http://svn.apache.org/viewvc/sling/site/trunk/content/documentation/development/sling-mock.mdtext?rev=1631696&r1=1631695&r2=1631696&view=diff
==============================================================================
--- sling/site/trunk/content/documentation/development/sling-mock.mdtext (original)
+++ sling/site/trunk/content/documentation/development/sling-mock.mdtext Tue Oct 14 09:31:12 2014
@@ -116,7 +116,7 @@ repository.
This pages lists all resource resolver types currently supported.
-#### RESOURCERESOLVER_MOCK (default)
+**RESOURCERESOLVER_MOCK (default)**
* Simulates an In-Memory resource tree, does not provide adaptions to JCR API.
* Based on the [Sling resourceresolver-mock implementation][resourceresolver-mock] implementation
@@ -124,13 +124,13 @@ This pages lists all resource resolver t
* Behaves slightly different from JCR resource mapping e.g. handling binary and date values.
* This resource resolver type is very fast because data is stored in memory and no JCR mapping is applied.
-#### JCR_MOCK
+**JCR_MOCK**
* Based on the [JCR Mocks][jcr-mock] implementation
* Uses the productive [Sling JCR resource provider implementation][jcr-resource] internally to do the Resource-JCR mapping
* Is quite fast because data is stored only in-memory
-#### JCR_JACKRABBIT
+**JCR_JACKRABBIT**
* Uses a real JCR Jackrabbit implementation (not Oak) as provided by [sling/commons/testing][sling-comons-testing]
* Full JCR/Sling features supported e.g. observations manager, transactions, versioning