svn commit: r1548202 - /jackrabbit/oak/trunk/oak-doc/src/site/markdown/differences_user.md

[an...@apache.org]

Author: angela
Date: Thu Dec  5 16:42:57 2013
New Revision: 1548202

URL: http://svn.apache.org/r1548202
Log:
OAK-791 - UserManagement: Document changes wrt Jackrabbit 2

Modified:
    jackrabbit/oak/trunk/oak-doc/src/site/markdown/differences_user.md

Modified: jackrabbit/oak/trunk/oak-doc/src/site/markdown/differences_user.md
URL: http://svn.apache.org/viewvc/jackrabbit/oak/trunk/oak-doc/src/site/markdown/differences_user.md?rev=1548202&r1=1548201&r2=1548202&view=diff
==============================================================================
--- jackrabbit/oak/trunk/oak-doc/src/site/markdown/differences_user.md (original)
+++ jackrabbit/oak/trunk/oak-doc/src/site/markdown/differences_user.md Thu Dec  5 16:42:57 2013
@@ -154,10 +154,20 @@ will limit the size of the multi value p
 
 ###### Upgrading Groups from Jackrabbit 2.x to OAK content structure
 
-**TODO**
+Upon upgrade from a Jackrabbit 2.x repository to OAK the group member lists that
+adjusted to reflect the new content structure as created by the OAK user management
+implementation; this means that the group member node structure will be changed
+by the migration process. Applications that rely on these implementation
+details of Jackrabbit 2.x user management instead of use the corresponding
+API calls will need to be modified accordingly.
 
 ###### Importing Group Members
-Importing group members through the import methods in `javax.jcr.Session` or `javax.jcr.Workspace` is storage agnostic and supports both, property based and node based, strategies and is backward compatible to content exported from Jackrabbit 2.x. The group member lists that are modified during an import are internally processed using the normal user manager APIs. This implies that the node structure after the import might not be the same as the one represented in the input.
+Importing group members through the import methods in `javax.jcr.Session` or
+`javax.jcr.Workspace` is storage agnostic and supports both, property based and
+node based, strategies and is backward compatible to content exported from
+Jackrabbit 2.x. The group member lists that are modified during an import are
+internally processed using the normal user manager APIs. This implies that the
+node structure after the import might not be the same as the one represented in the input.
 
 #### 2. Builtin Users
 The setup of builtin user and group accounts is triggered by the configured `WorkspaceInitializer` associated with the user management configuration (see Configuration section below).