Hi Devs,
I have a requirement to customize XWiki to integrate with Communities in
a Social Networking Site that I am developing. Members of a Community
should be able to view/edit documents created by other members of the
same community but they should not be able to view/edit documents
created by members of other communities. Essentially, we want to
introduce a 'Community Scope' in XWiki.
The number of communities and members grows with time, obviously.
I think such a feature is not available out of the box. I am planning to
do some customization on the Groups feature of XWiki to achieve this
requirement.
Here is an outline of the approach.
1. When a new community gets created in the social site, create a new
Group of corresponding name in XWiki programatically. (need to know what
API to call).
2. When a user joins a community, automatically add the user to the
XWiki group associated to that community.
3. When a user creates a new document in the community's XWiki, gives
rights to the associated community's Group to that document.
The Rights module of XWiki will automatically take care of the
authorization when that document is requested by any user.
The challenge seems to be identifying the right places in code to make
changes for 1 and 3. (#2 I can try to achieve by overriding
XWikiUser.isUserInGroup() to plugin my custom implementation).
Any pointer in this regard will be greatly appreciated. If there is an
alternative approach to what I am planning, that would be great too.
Thanks,
Rupinder
Please do not print this email unless it is absolutely necessary.
The information contained in this electronic message and any attachments to this message
are intended for the exclusive use of the addressee(s) and may contain proprietary,
confidential or privileged information. If you are not the intended recipient, you should
not disseminate, distribute or copy this e-mail. Please notify the sender immediately and
destroy all copies of this message and any attachments.
WARNING: Computer viruses can be transmitted via email. The recipient should check this
email and any attachments for the presence of viruses. The company accepts no liability
for any damage caused by any virus transmitted by this email.
www.wipro.com