Create a group

[anthonyNkuinjeu]

Hello Sir, We have a problem about the difference between "group", "role" and "community".

• So, do we have to create a class named "LdapCommunity" like "LdapGroup" ? In that way, we could attach to each LdapCommunity instance a subdirectory that is dedicated to the roles (group). For example, the IF14 Community could have two subdirectories designed for the roles "teacher"and "students". To summerize, the community "IF14" will be the child of the root and the roles "teachers" and "students" will be the children of the community "IF14".
• The second way of doing this. Not create the Ldap class "LdapCommunity" and just add the name of the community concerned in the name of the role. For exemple, I want to create the role "teachers" for the IF14 community. So, in the java code I do:

String name__of_therole = "IF14" + nameOfTheRole;

And I just use the new name "IF14_teachers" for the creation of the role. In a nutshell , all the roles will be the children of the root and to retrieve a specific role, I will have to look at the prefix name (IF14 in that case).

Tell us which way you see things. Personnally, I was already developing the first solution but I don't think it is what you want.

[benel]

• Communities have nothing to do with LDAP. They are just a way to setup the look of Dolomite depending on the URL that was used to launch Dolomite. For now, they are stored in the configuration file (see installation instructions). They will be stored in the database instead so that users can create them.
• There are no association between communities and roles, so no defined cardinality either. You're right to say that a role could be "IF14 student" but it could be "UTT student" as well.

Don't make it too complex. You just need a "Community" MVC model with existing attributes (dolomite URL, name, application URL) + welcome text.