From 7f06c21ba00dc82b8d5c3f4d5b56448cf3322675 Mon Sep 17 00:00:00 2001 From: giangtran Date: Tue, 22 May 2012 15:44:08 +0700 Subject: [PATCH] DOC-1563 Fix incorrect texts --- .../en/en-US/Application/Application.wiki | 2 +- .../en/en-US/Application/List_of_Gadgets.wiki | 2 +- .../Configuration_introduction.wiki | 3 +- .../Spaces_Template_Configuration.wiki | 4 +- .../Create_i18n_activities.wiki | 4 +- ...veloper_Documentation_Activity_Plugin.wiki | 10 +- ...veloper_Documentation_Activity_Stream.wiki | 6 +- .../Developer_Documentation_OpenSocial.wiki | 10 +- .../Developer_Documentation_People.wiki | 8 +- .../Developer_Documentation_Spaces.wiki | 2 +- .../Developer_References.wiki | 2 +- ...ow_to_extend_the_activities_rendering.wiki | 2 +- .../en-US/DeveloperReference/Java_APIs.wiki | 102 +++++++++--------- .../Overrideable_components.wiki | 2 +- .../Production_Deployment_Tutorial.wiki | 10 +- .../DeveloperReference/Rest_Service_APIs.wiki | 6 +- .../Space_Portlet_Preference.wiki | 2 +- .../DeveloperReference/XMLProcessor.wiki | 4 +- .../DeveloperReference/widget_tutorial.wiki | 8 +- .../wikbook/en/en-US/jcr_structure.wiki | 18 ++-- 20 files changed, 103 insertions(+), 104 deletions(-) diff --git a/docs/refguide/src/main/resources/wikbook/en/en-US/Application/Application.wiki b/docs/refguide/src/main/resources/wikbook/en/en-US/Application/Application.wiki index 2b0b115241..97c7117c23 100644 --- a/docs/refguide/src/main/resources/wikbook/en/en-US/Application/Application.wiki +++ b/docs/refguide/src/main/resources/wikbook/en/en-US/Application/Application.wiki @@ -1,4 +1,4 @@ -This chapter provides you a comprehensive view about applications in eXo Social, including: +This chapter provides you a comprehensive view about applications in Social, including: * [Portlets|#SOCref.Portlets] * [Gadgets|#SOCref.List_Of_Gadget_in_Social] diff --git a/docs/refguide/src/main/resources/wikbook/en/en-US/Application/List_of_Gadgets.wiki b/docs/refguide/src/main/resources/wikbook/en/en-US/Application/List_of_Gadgets.wiki index cecb0543de..9bc4709037 100644 --- a/docs/refguide/src/main/resources/wikbook/en/en-US/Application/List_of_Gadgets.wiki +++ b/docs/refguide/src/main/resources/wikbook/en/en-US/Application/List_of_Gadgets.wiki @@ -1,4 +1,4 @@ -All eXo Social gadgets are in _opensocial.war_. +All Social gadgets are in _opensocial.war_. h1. Activity Stream {anchor:id=SOCref.List_Of_Gadget_in_Social.ActivityStream} * *Description*: Manage activities of users: update status, like/unlike activities, comment activities, delete activities and delete comments. diff --git a/docs/refguide/src/main/resources/wikbook/en/en-US/Configuration/Configuration_introduction.wiki b/docs/refguide/src/main/resources/wikbook/en/en-US/Configuration/Configuration_introduction.wiki index ed1071d587..327068072e 100644 --- a/docs/refguide/src/main/resources/wikbook/en/en-US/Configuration/Configuration_introduction.wiki +++ b/docs/refguide/src/main/resources/wikbook/en/en-US/Configuration/Configuration_introduction.wiki @@ -1,5 +1,4 @@ -This chapter describes about configurations used in eXo Social. It consists of the following main sections: +This chapter describes about configurations used in Social. It consists of the following main sections: * [Components|#SOCref.Configuration.Component] * [External component plugins|#SOCref.Configuration.External_component_plugins] - diff --git a/docs/refguide/src/main/resources/wikbook/en/en-US/Configuration/Spaces_Template_Configuration.wiki b/docs/refguide/src/main/resources/wikbook/en/en-US/Configuration/Spaces_Template_Configuration.wiki index 2d2061299a..797c3879ee 100644 --- a/docs/refguide/src/main/resources/wikbook/en/en-US/Configuration/Spaces_Template_Configuration.wiki +++ b/docs/refguide/src/main/resources/wikbook/en/en-US/Configuration/Spaces_Template_Configuration.wiki @@ -1,4 +1,4 @@ -In eXo Social, you may have two space types (classic and webos spaces). +In Social, you may have two space types (classic and webos spaces). For the classic space, you can pre-configure the template. You can configure the layout to select where to display the applications (for example, the application's menu on the left, the selected application is displayed on the right, and more). @@ -55,7 +55,7 @@ If you want to put the menu on the right and the application on the left, you ca {code} -In eXo Social standalone, this configuration file is at: +In Social standalone, this configuration file is at: * _{{{$EXO_TOMCAT/webapps/socialdemo/WEB-INF/conf/portal/template/pages/space/page.xml}}}_ In eXo Platform, this configuration file is at: * _{{{$EXO_TOMCAT/webapps/{portal-name}/WEB-INF/conf/portal/template/pages/space/page.xml}}}_ diff --git a/docs/refguide/src/main/resources/wikbook/en/en-US/DeveloperReference/Create_i18n_activities.wiki b/docs/refguide/src/main/resources/wikbook/en/en-US/DeveloperReference/Create_i18n_activities.wiki index 894acb2308..d5249414d5 100644 --- a/docs/refguide/src/main/resources/wikbook/en/en-US/DeveloperReference/Create_i18n_activities.wiki +++ b/docs/refguide/src/main/resources/wikbook/en/en-US/DeveloperReference/Create_i18n_activities.wiki @@ -1,7 +1,7 @@ -This section will show you how to internationalize activities in eXo Social. +This section will show you how to internationalize activities in Social. h1. Internationalize an activity {anchor:id="SOCref.Developers_References.How_to_create_i18n_activities.I18n_activities"} -In the previous versions, eXo Social had hard-coded messages for activities, such as +In the previous versions, Social had hard-coded messages for activities, such as creating spaces, granting the "manager" role to a member, sending connection request to another user, updating a user's profile/avatar, and more. And now, to internationalize these types of messages, you can use resource bundles and _I18NActivityProcessor_. diff --git a/docs/refguide/src/main/resources/wikbook/en/en-US/DeveloperReference/Developer_Documentation_Activity_Plugin.wiki b/docs/refguide/src/main/resources/wikbook/en/en-US/DeveloperReference/Developer_Documentation_Activity_Plugin.wiki index 3581d3d8a9..b600ef85d8 100644 --- a/docs/refguide/src/main/resources/wikbook/en/en-US/DeveloperReference/Developer_Documentation_Activity_Plugin.wiki +++ b/docs/refguide/src/main/resources/wikbook/en/en-US/DeveloperReference/Developer_Documentation_Activity_Plugin.wiki @@ -14,11 +14,11 @@ The Project Code is available [here.|http://wiki.exoplatform.org/xwiki/bin/downl When an activity is displayed, UIActivityFactory will look for its registered custom actvity display by activity's type. If not found, UIDefaultActivity will be called for displaying that activity. -For example, in eXo Social, there is an activity of type "exosocial:spaces" created by SpaceActivityPublisher, but now, you want to display it without own UI component instead of the default one. To do that, follow these steps. +For example, in Social, there is an activity of type "exosocial:spaces" created by SpaceActivityPublisher, but now, you want to display it without own UI component instead of the default one. To do that, follow these steps. *1.* Create a sample project: -{screen} +{code} mvn archetype:generate [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'archetype'. @@ -65,7 +65,7 @@ artifactId: exo.social.samples.activity-plugin version: 1.0.0-SNAPSHOT package: org.exoplatform.social.samples.activityPlugin Y: y -{screen} +{code} *2.* Edit the _pom.xml_ file as below. @@ -569,7 +569,7 @@ Currently, you have to copy and paste in the template file. By this way, you hav {note} h3. What is ActivityBuilder? {anchor:id=Developer_document.What_is_activity_builder} -ActivityBuilder is one class which is used to get values of _ExoSocialActivity_ to set to UIActivity for displaying. eXo Social provides the BaseUIActivityBuilder class for developers to extend and customize their own activity builder easily and properly. +ActivityBuilder is one class which is used to get values of _ExoSocialActivity_ to set to UIActivity for displaying. Social provides the BaseUIActivityBuilder class for developers to extend and customize their own activity builder easily and properly. For example, to write your own UILinkActivityBuilder, you just need to extend BaseUIActivityBuilder and then customize attributes and behaviors of the activity builder as below. @@ -594,7 +594,7 @@ To learn more about ActivityBuilder, refer to the [BaseUIActivity class.|http:// {note} h2. Create a composer extension for composing activity on the UI composer and display it on the activity stream {anchor:id=Developer_document.Create_composer_extension} -The UIActivityComposer is an extended class of UIContainer that is used to display inputs for users to create their own activities. To write your own activity composer, it is recommended that you use the UIActivityComposer available in eXo Social. +The UIActivityComposer is an extended class of UIContainer that is used to display inputs for users to create their own activities. To write your own activity composer, it is recommended that you use the UIActivityComposer available in Social. For example, to create an input component for inserting video links into your activity, do the following steps: diff --git a/docs/refguide/src/main/resources/wikbook/en/en-US/DeveloperReference/Developer_Documentation_Activity_Stream.wiki b/docs/refguide/src/main/resources/wikbook/en/en-US/DeveloperReference/Developer_Documentation_Activity_Stream.wiki index cdb4f01a2f..6e052ea96e 100644 --- a/docs/refguide/src/main/resources/wikbook/en/en-US/DeveloperReference/Developer_Documentation_Activity_Stream.wiki +++ b/docs/refguide/src/main/resources/wikbook/en/en-US/DeveloperReference/Developer_Documentation_Activity_Stream.wiki @@ -1,4 +1,4 @@ -eXo Social provides users with a way to share their activity information (also known as Activity Stream) and collaborate in spaces (also known as group work). With the API, you can customize the way to display activities or publish new ones. +Social provides users with a way to share their activity information (also known as Activity Stream) and collaborate in spaces (also known as group work). With the API, you can customize the way to display activities or publish new ones. To manipulate activities, you need to use the _AtivityManager_ service. h1. Publish an activity {anchor:id=SOCref.Developer_references.PublishActivity} @@ -209,7 +209,7 @@ The "init-params" contains all the key-value data which a processor will use to h1. Publish an RSS feed with feedmash {anchor:id=SOCref.Developer_references.Publish_an_rss_feed_with_feedmash} -It is really easy to publish an RSS feed to a space's activity stream. eXo Social provides _FeedmashJobPlugin_ to publish the RSS feeds. As you can see in the project "_exo.social.extras.feedmash_", there are the _JiraFeedConsumer_ and _HudsonFeedConsumer_ samples to post eXo Social project's feeds (jira and hudson) to a pre-defined space named _exosocial_ in a specific portal container named _socialdemo_ as in the configuration file: +It is really easy to publish an RSS feed to a space's activity stream. Social provides _FeedmashJobPlugin_ to publish the RSS feeds. As you can see in the project "_exo.social.extras.feedmash_", there are the _JiraFeedConsumer_ and _HudsonFeedConsumer_ samples to post Social project's feeds (jira and hudson) to a pre-defined space named _exosocial_ in a specific portal container named _socialdemo_ as in the configuration file: {code:xml} @@ -268,7 +268,7 @@ It is really easy to publish an RSS feed to a space's activity stream. eXo Socia {code} -Run eXo Social with the URL: http://localhost:8080/socialdemo, then log in and create a space named "exosocial". After creating the "exosocial" space, all the feeds of the eXo Social project on Jira and Hudson will be automatically published to the _exosocial_ space. +Run Social with the URL: http://localhost:8080/socialdemo, then log in and create a space named "exosocial". After creating the "exosocial" space, all the feeds of the Social project on Jira and Hudson will be automatically published to the _exosocial_ space. h1. Sample Code {anchor:id=SOCref.Developer_references.Sample_code} See the following code snippet to know more details about how to publish an activity and add comments to an activity: diff --git a/docs/refguide/src/main/resources/wikbook/en/en-US/DeveloperReference/Developer_Documentation_OpenSocial.wiki b/docs/refguide/src/main/resources/wikbook/en/en-US/DeveloperReference/Developer_Documentation_OpenSocial.wiki index a60f4cb9af..7a2f0da08f 100644 --- a/docs/refguide/src/main/resources/wikbook/en/en-US/DeveloperReference/Developer_Documentation_OpenSocial.wiki +++ b/docs/refguide/src/main/resources/wikbook/en/en-US/DeveloperReference/Developer_Documentation_OpenSocial.wiki @@ -1,5 +1,5 @@ -eXo Social supports the OpenSocial standard. So you can integrate OpenSocial gadgets in your dashboard and use the RPC or REST service to view or publish the social data. -With the support for the OpenSocial standard, eXo Social provides a framework for developers to build gadgets that can display and mash up activity information for contacts, social networks, applications and services. +Social supports the OpenSocial standard. So you can integrate OpenSocial gadgets in your dashboard and use the RPC or REST service to view or publish the social data. +With the support for the OpenSocial standard, Social provides a framework for developers to build gadgets that can display and mash up activity information for contacts, social networks, applications and services. h1. Gadget {anchor:id=Developer_document.Open_social.Gadget} @@ -14,11 +14,11 @@ To know how to create an OpenSocial gadget, see [here|http://wiki.opensocial.org {note} Gadgets will work out of the box on Dashboard. In eXo, gadgets are wrapped by GadgetWrapperPortlet so they can work as any other portlet applications. -At present, eXo Social supports [OpenSocial Specification v1.1| http://opensocial-resources.googlecode.com/svn/spec/1.1/OpenSocial-Specification.xml]. +At present, Social supports [OpenSocial Specification v1.1| http://opensocial-resources.googlecode.com/svn/spec/1.1/OpenSocial-Specification.xml]. {note} h2. Supported APIs {anchor:id=Developer_document.Open_social.Supported_APIs} -eXo Social leverages [Apache Shindig|http://shindig.apache.org/overview.html] - an OpenSocial reference implementation to provide and extend OpenSocial APIs which is compatible with the common OpenSocial APIs which is supported by other big social networks like [Ning|http://www.ning.com], [Hi5|http://www.hi5.com], [Orkut|http://www.orkut.com] and more. +Social leverages [Apache Shindig|http://shindig.apache.org/overview.html] - an OpenSocial reference implementation to provide and extend OpenSocial APIs which is compatible with the common OpenSocial APIs which is supported by other big social networks like [Ning|http://www.ning.com], [Hi5|http://www.hi5.com], [Orkut|http://www.orkut.com] and more. To get more details about Supported APIs, refer to [OpenSocial Specification|http://docs.opensocial.org/display/OSD/Specs]. @@ -82,5 +82,5 @@ After using the OpenSocial Java library and Groovy, your code will look like thi In the example above, the groupId is set to "space:bookflow" and bookflow is the name of the space. h1. Tutorial {anchor:id=Developer_document.Open_social.Tutorial} -* See [Grails + eXo Social tutorial.|http://www.exoplatform.com/company/public/website/resource-viewer?path=/website/Content%20types/Tutorial/grails-exo-social] +* See [Grails + Social tutorial.|http://www.exoplatform.com/company/public/website/resource-viewer?path=/website/Content%20types/Tutorial/grails-exo-social] diff --git a/docs/refguide/src/main/resources/wikbook/en/en-US/DeveloperReference/Developer_Documentation_People.wiki b/docs/refguide/src/main/resources/wikbook/en/en-US/DeveloperReference/Developer_Documentation_People.wiki index ed5fe3a3f9..3fef85d4b6 100644 --- a/docs/refguide/src/main/resources/wikbook/en/en-US/DeveloperReference/Developer_Documentation_People.wiki +++ b/docs/refguide/src/main/resources/wikbook/en/en-US/DeveloperReference/Developer_Documentation_People.wiki @@ -1,10 +1,10 @@ -eXo Social provides a way to manage profile information, and connections between users. With the APIs provided, you can easily add, manage and customize information and relationships of users. +Social provides a way to manage profile information, and connections between users. With the APIs provided, you can easily add, manage and customize information and relationships of users. h1. Identity {anchor:id=SOCref.Developers_References.People.Identity} -The identity allows identifying a unique social object. The eXo Social objects can be person, group, application, or whatever related to social interactions, such as connecting, publishing an activity stream or holding a user profile. +The identity allows identifying a unique social object. The Social objects can be person, group, application, or whatever related to social interactions, such as connecting, publishing an activity stream or holding a user profile. h2. IdentityProvider {anchor:id=SOCref.Developers_References.People.IdentityProvider} -eXo Social provides IdentityProvider as an identiy mechanism for the third parties to extend eXo Social's identity system without any limitation. Here is an example: +Social provides IdentityProvider as an identiy mechanism for the third parties to extend Social's identity system without any limitation. Here is an example: {code:java} class SampleIdentityProvider extends OrganizationIdentityProvider{ @@ -112,7 +112,7 @@ public class ProfileLoggerListener extends ProfileListenerPlugin{ h1. Connections {anchor:id=SOCref.Developers_References.People.Relationships} Similarly, you can apply the above steps to implement _RelationshipListenerPlugin_ for relationship notifications. -Relationship is the bridge between two identities in eXo Social. There are many types of relationships defined in the Relationship class. With these types, a user can invite another user, confirm invitations or remove relationship. +Relationship is the bridge between two identities in Social. There are many types of relationships defined in the Relationship class. With these types, a user can invite another user, confirm invitations or remove relationship. h2. Users connection {anchor:id=SOCref.Developers_References.People.Connecting_users} diff --git a/docs/refguide/src/main/resources/wikbook/en/en-US/DeveloperReference/Developer_Documentation_Spaces.wiki b/docs/refguide/src/main/resources/wikbook/en/en-US/DeveloperReference/Developer_Documentation_Spaces.wiki index bf03fa4b98..9c4648fdd8 100644 --- a/docs/refguide/src/main/resources/wikbook/en/en-US/DeveloperReference/Developer_Documentation_Spaces.wiki +++ b/docs/refguide/src/main/resources/wikbook/en/en-US/DeveloperReference/Developer_Documentation_Spaces.wiki @@ -1,4 +1,4 @@ -eXo Social provides a way to create groups and to share data and applications by spaces. A space has its own activity stream in which applications or members can publish information. In each space, members use applications together with shared data. +Social provides a way to create groups and to share data and applications by spaces. A space has its own activity stream in which applications or members can publish information. In each space, members use applications together with shared data. To manipulate the spaces, you will use the SpaceService. To get an instance of this class, you need to get the current _PortalContainer_ instance. diff --git a/docs/refguide/src/main/resources/wikbook/en/en-US/DeveloperReference/Developer_References.wiki b/docs/refguide/src/main/resources/wikbook/en/en-US/DeveloperReference/Developer_References.wiki index 8debf01f3e..70a1dbe3cd 100644 --- a/docs/refguide/src/main/resources/wikbook/en/en-US/DeveloperReference/Developer_References.wiki +++ b/docs/refguide/src/main/resources/wikbook/en/en-US/DeveloperReference/Developer_References.wiki @@ -9,4 +9,4 @@ This chapter supplies you with the basic knowledge about the following topics: * [Public Javascript APIs|#SOCref.DevelopersReferences.PublicJavascriptAPIs] * [Social JCR Structure|#SOCref.Social_JCR_Structure] -With this knowledge, you can extend more functions for eXo Social, or customize them as you want. \ No newline at end of file +With this knowledge, you can extend more functions for Social, or customize them as you want. \ No newline at end of file diff --git a/docs/refguide/src/main/resources/wikbook/en/en-US/DeveloperReference/How_to_extend_the_activities_rendering.wiki b/docs/refguide/src/main/resources/wikbook/en/en-US/DeveloperReference/How_to_extend_the_activities_rendering.wiki index 438bb73ba4..fb5fc6d6d6 100644 --- a/docs/refguide/src/main/resources/wikbook/en/en-US/DeveloperReference/How_to_extend_the_activities_rendering.wiki +++ b/docs/refguide/src/main/resources/wikbook/en/en-US/DeveloperReference/How_to_extend_the_activities_rendering.wiki @@ -18,7 +18,7 @@ But you may want to support a special syntax, for example: You can have more sophisticated cases to process, such as parsing the link that include in the activity's content. Because a process actually has the full access to the Activity, you can very well process based on the owner, app, and media item. h1. Write an ActivityProcessor {anchor:id=SOCref.DeveloperReferences.how_extend_the_activities_rendering._write_ActivityProcessor} -eXo Social lets you pre-process an activity before it is returned by the ActivityManager. To do this, you simply need to implement the interface ActivityProcessor: +Social lets you pre-process an activity before it is returned by the ActivityManager. To do this, you simply need to implement the interface ActivityProcessor: {code:java} /** diff --git a/docs/refguide/src/main/resources/wikbook/en/en-US/DeveloperReference/Java_APIs.wiki b/docs/refguide/src/main/resources/wikbook/en/en-US/DeveloperReference/Java_APIs.wiki index 77b486f252..fed0601e4d 100644 --- a/docs/refguide/src/main/resources/wikbook/en/en-US/DeveloperReference/Java_APIs.wiki +++ b/docs/refguide/src/main/resources/wikbook/en/en-US/DeveloperReference/Java_APIs.wiki @@ -18,7 +18,7 @@ h1. ActivityManager {anchor:id=Developer_document.Java_APIs.Activity_Manager} |*removeLike*(ExoSocialActivity activity, Identity identity) throws ActivityStorageException | {{ activity}}, {{identity}} - a user who dislikes an activity |void|Remove an identity who likes an activity, if this activity is liked, it will be removed.| |*getComments*(ExoSocialActivity activity) throws ActivityStorageException | {{activity}} |List| Get the comment list of an activity.| |*recordActivity*(Identity owner, String type, String title) throws ActivityStorageException | {{owner, type, title }} |ExoSocialActivity |Record an activity. (Since 1.2.0-GA).| -|*recordActivity*(Identity owner, ExoSocialActivity activity) throws Exception | {{owner, activity }} |ExoSocialActivity |Save an activity. You should use ActivityManager#saveActivity(org.exoplatform.social.core.identity.model.Identity, org.exoplatform.social.core.activity.model.ExoSocialActivity) instead. It will be removed in eXo Social 1.3.x.| +|*recordActivity*(Identity owner, ExoSocialActivity activity) throws Exception | {{owner, activity }} |ExoSocialActivity |Save an activity. You should use ActivityManager#saveActivity(org.exoplatform.social.core.identity.model.Identity, org.exoplatform.social.core.activity.model.ExoSocialActivity) instead. It will be removed in Social 1.3.x.| |*recordActivity*(Identity owner, String type, String title, String body) throws ActivityStorageException | {{ owner}} - the owner of the target stream for this activity, {{type}} - the type of an activity which will be used to render a custom UI, {{title}} - the title, {{body}} - the body |ExoSocialActivity |Record an activity.| |*addProcessor*(ActivityProcessor processor) | {{processor }} |void|Add a new processor.| |*addProcessorPlugin*(BaseActivityProcessorPlugin plugin) | {{plugin}} |void|Add a new processor plugin.| @@ -135,40 +135,40 @@ h1. SpaceService {anchor:id=Developer_document.JavaAPIs.Java_APIs.SpaceService} |*unregisterSpaceListenerPlugin*(SpaceListenerPlugin spaceListenerPlugin)|{{spaceListenerPlugin}}|void|Unregister an existing space listener plugin. (Since 1.2.0-GA).| |*setSpaceApplicationConfigPlugin*(SpaceApplicationConfigPlugin spaceApplicationConfigPlugin)|{{spaceApplicationConfigPlugin}}|void|Set a space application configuration plugin to configure the home and space applications. By configuring this, the space service will know how to create a new page node with title, URL, and portlet to use. (Since 1.2.0-GA). | |*getSpaceApplicationConfigPlugin*()|{{N/A}}|SpaceApplicationConfigPlugin|Get the configuration of applications to be initialized when creating a new space. (Since 1.2.0-GA).| -|*getAllSpaces*() throws SpaceException|{{N/A}}|List|Get all spaces in eXo Social. You should use method getAllSpaceWithListAccess instead of getAllSpaces. It will be removed in eXo Social 1.3.x.| +|*getAllSpaces*() throws SpaceException|{{N/A}}|List|Get all spaces in Social. You should use method getAllSpaceWithListAccess instead of getAllSpaces. It will be removed in Social 1.3.x.| |*getSpaceByName*(String spaceName) throws SpaceException|{{spaceName}}|Space|Get a space by its name. You should use SpaceService#getSpaceByPrettyName instead. It will be removed version 1.3.x.| |*getSpacesByFirstCharacterOfName*(String firstCharacterOfName) throws SpaceException|{{firstCharacterOfName}}| List |Get all spaces whose name starting with the input character.| |*getSpacesBySearchCondition*(String condition) throws Exception|{{condition}} | List |Get all spaces which has the name or the description that matches the input condition.| -|*getSpaces*(String userId) throws SpaceException|{{userId}} | List|Get spaces of a user in which that user is a member. You should use getMemberSpaces(String) instead. It will be removed in eXo Social 1.3.x| -|*getAccessibleSpaces*(String userId) throws SpaceException|{{userId}}|List|Get spaces of a user which that user has the access permission. You should use getAccessibleSpacesWithListAccess(String) instead. It will be removed in eXo Social 1.3.x.| -|*getEditableSpaces*(String userId) throws SpaceException|{{userId}}| List|Get spaces of a user which that user has the edit permission. You should use getSettingableSpaces(String) instead. It will be removed in eXo Social 1.3.x.| -|*getInvitedSpaces*(String userId) throws SpaceException|{{userId}}| List |Get invited spaces of a user and that user can accept or deny the request. You should use getInvitedSpacesWithListAccess(String) instead. It will be removed in eXo Social 1.3.x.| -|*getPublicSpaces*(String userId) throws SpaceException|{{userId - Id of user}}|List |Get invited spaces of a user that can be accepted or denied by the user. You should use getPublicSpacesWithListAccess(String) instead. It will be removed in eXo Social 1.3.x.| -|*getPendingSpaces*(String userId) throws SpaceException|{{userId}}| List |Get pending spaces of a user and spaces which the user can revoke that request. You should use getPendingSpacesWithListAccess(String) instead. It will be removed in eXo Social 1.3.x.| +|*getSpaces*(String userId) throws SpaceException|{{userId}} | List|Get spaces of a user in which that user is a member. You should use getMemberSpaces(String) instead. It will be removed in Social 1.3.x| +|*getAccessibleSpaces*(String userId) throws SpaceException|{{userId}}|List|Get spaces of a user which that user has the access permission. You should use getAccessibleSpacesWithListAccess(String) instead. It will be removed in Social 1.3.x.| +|*getEditableSpaces*(String userId) throws SpaceException|{{userId}}| List|Get spaces of a user which that user has the edit permission. You should use getSettingableSpaces(String) instead. It will be removed in Social 1.3.x.| +|*getInvitedSpaces*(String userId) throws SpaceException|{{userId}}| List |Get invited spaces of a user and that user can accept or deny the request. You should use getInvitedSpacesWithListAccess(String) instead. It will be removed in Social 1.3.x.| +|*getPublicSpaces*(String userId) throws SpaceException|{{userId - Id of user}}|List |Get invited spaces of a user that can be accepted or denied by the user. You should use getPublicSpacesWithListAccess(String) instead. It will be removed in Social 1.3.x.| +|*getPendingSpaces*(String userId) throws SpaceException|{{userId}}| List |Get pending spaces of a user and spaces which the user can revoke that request. You should use getPendingSpacesWithListAccess(String) instead. It will be removed in Social 1.3.x.| |*createSpace*(Space space, String creator, String invitedGroupId) throws SpaceException|{{space, creator, invitedGroupId}}|Space|Create a new space and invite all users from invitedGroupId to join this newly created space.| -|*saveSpace*(Space space, boolean isNew) throws SpaceException|{{space}}, {{isNew}}|void|Save a new space or update a space. You should use updateSpace(org.exoplatform.social.core.space.model.Space) instead. It will be removed in eXo Social 1.3.x.| -|*deleteSpace*(String spaceId) throws SpaceException|{{ spaceId}}|void|Delete a space by its id. You should use deleteSpace(org.exoplatform.social.core.space.model.Space) instead. It will be removed in eXo Social 1.3.x.| -|*initApp*(Space space) throws SpaceException|{{space}}|void|It is just for compatibility. Deprecated: it will be removed in eXo Social 1.3.x.| -|*initApps*(Space space) throws SpaceException|{{space}}|void|It is just for compatibility. Deprecated: it will be removed in eXo Social 1.3.x.| -|*deInitApps*(Space space) throws SpaceException|{{space }}| void |It is just for compatibility. Deprecated: it will be removed in eXo Social 1.3.x.| -|*addMember*(String spaceId, String userId) throws SpaceException|{{spaceId, userId}}|void|Add a user to a space, the user will get the "member" role in a space. You should use addMember(org.exoplatform.social.core.space.model.Space, String) instead. It will be removed in eXo Social 1.3.x.| -|*removeMember*(String spaceId, String userId) throws SpaceException|{{spaceId, userId}}|void|Remove a member from a space. You should use removeMember(org.exoplatform.social.core.space.model.Space, String) instead. It will be removed in eXo Social 1.3.x.| -|*getMembers*(Space space) throws SpaceException|{{space}}| List|Get a list of the space members from a space. You should use Space#getMembers() instead. It will be removed in eXo Social 1.3.x.| -|*getMembers*(String spaceId) throws SpaceException|{{spaceId}}| List|Get a list of the space members from a space. You should use Space#getMembers() instead. It will be removed in eXo Social 1.3.x.| -|*setLeader*(Space space, String userId, boolean isLeader) throws SpaceException|{{space, userId, isLeader }}|void|Set a member of a space as a manager. You should use setManager(org.exoplatform.social.core.space.model.Space, String, boolean) instead. It will be removed in eXo Social 1.3.x.| -|*setLeader*(String spaceId, String userId, boolean isLeader) throws SpaceException|{{spaceId, userId, isLeader}}|void|Set a member of a space as a manager. You should use setManager(org.exoplatform.social.core.space.model.Space, String, boolean) instead. It will be removed in eXo Social 1.3.x.| -|*isLeader*(Space space, String userId) throws SpaceException|{{space, userId}}|boolean |Check whether a user is a space's leader or not. You should use isManager(org.exoplatform.social.core.space.model.Space, String) instead. It will be removed in eXo Social 1.3.x.| -|*isLeader*(String spaceId, String userId) throws SpaceException|{{spaceId, userId}}|boolean |Check whether a user is a space's leader or not. You should use isManager(org.exoplatform.social.core.space.model.Space, String) instead. It will be removed in eXo Social 1.3.x.| -|*isOnlyLeader*(Space space, String userId) throws SpaceException|{{space, userId}}|boolean|Check whether a user is the only leader of a space or not. You should use isOnlyManager(org.exoplatform.social.core.space.model.Space, String) instead. It will be removed in eXo Social 1.3.x.| -|*isOnlyLeader*(String spaceId, String userId) throws SpaceException|{{spaceId, userId}}|boolean|Check whether a user is the only leader of a space or not. You should use isOnlyManager(org.exoplatform.social.core.space.model.Space, String) instead. It will be removed in eXo Social 1.3.x.| -|*isMember*(String spaceId, String userId) throws SpaceException|{{spaceId, userId, }}| boolean |Check whether a user is a space's member or not. You should use isMember(org.exoplatform.social.core.space.model.Space, String) instead. It will be removed in eXo Social 1.3.x.| -|*hasAccessPermission*(String spaceId, String userId) throws SpaceException|{{spaceId, userId}}|boolean |Check if a user can access a space or not. You should use hasAccessPermission(org.exoplatform.social.core.space.model.Space, String) instead. It will be removed in eXo Social 1.3.x.| -|*hasEditPermission*(Space space, String userId) throws SpaceException|{{space, userId}}|Boolean |Check if a user can have the edit permission of a space or not. You should use hasSettingPermission(org.exoplatform.social.core.space.model.Space, String) instead. It will be removed in eXo Social 1.3.x.| -|*hasEditPermission*(String spaceId, String userId) throws SpaceException|{{spaceId, userId}}|Boolean |Check if a user can have the edit permission of a space or not. You should use hasSettingPermission(org.exoplatform.social.core.space.model.Space, String) instead. It will be removed in eXo Social 1.3.x.| -|*isInvited*(Space space, String userId) throws SpaceException|{{space, userId}}|Boolean |Check if a user is in the invited list of a space or not. You should use isInvitedUser(org.exoplatform.social.core.space.model.Space, String) instead. It will be removed in eXo Social 1.3.x.| -|*isInvited*(String spaceId, String userId) throws SpaceException|{{spaceId, userId}}|Boolean |Check if a user is in the invited list of a space or not. You should use isInvitedUser(org.exoplatform.social.core.space.model.Space, String) instead. It will be removed in eXo Social 1.3.x.| -|*isPending*(Space space, String userId) throws SpaceException|{{space, userId}}|Boolean |Check if a user is in the pending list of a space or not.You should use isPendingUser(org.exoplatform.social.core.space.model.Space, String) instead. It will be removed in eXo Social 1.3.x.| -|*isPending*(String spaceId, String userId) throws SpaceException|{{spaceId, userId}}|Boolean | Check if a user is in the pending list of a space or not. You should use isPendingUser(org.exoplatform.social.core.space.model.Space, String) instead. It will be removed in eXo Social 1.3.x.| +|*saveSpace*(Space space, boolean isNew) throws SpaceException|{{space}}, {{isNew}}|void|Save a new space or update a space. You should use updateSpace(org.exoplatform.social.core.space.model.Space) instead. It will be removed in Social 1.3.x.| +|*deleteSpace*(String spaceId) throws SpaceException|{{ spaceId}}|void|Delete a space by its id. You should use deleteSpace(org.exoplatform.social.core.space.model.Space) instead. It will be removed in Social 1.3.x.| +|*initApp*(Space space) throws SpaceException|{{space}}|void|It is just for compatibility. Deprecated: it will be removed in Social 1.3.x.| +|*initApps*(Space space) throws SpaceException|{{space}}|void|It is just for compatibility. Deprecated: it will be removed in Social 1.3.x.| +|*deInitApps*(Space space) throws SpaceException|{{space }}| void |It is just for compatibility. Deprecated: it will be removed in Social 1.3.x.| +|*addMember*(String spaceId, String userId) throws SpaceException|{{spaceId, userId}}|void|Add a user to a space, the user will get the "member" role in a space. You should use addMember(org.exoplatform.social.core.space.model.Space, String) instead. It will be removed in Social 1.3.x.| +|*removeMember*(String spaceId, String userId) throws SpaceException|{{spaceId, userId}}|void|Remove a member from a space. You should use removeMember(org.exoplatform.social.core.space.model.Space, String) instead. It will be removed in Social 1.3.x.| +|*getMembers*(Space space) throws SpaceException|{{space}}| List|Get a list of the space members from a space. You should use Space#getMembers() instead. It will be removed in Social 1.3.x.| +|*getMembers*(String spaceId) throws SpaceException|{{spaceId}}| List|Get a list of the space members from a space. You should use Space#getMembers() instead. It will be removed in Social 1.3.x.| +|*setLeader*(Space space, String userId, boolean isLeader) throws SpaceException|{{space, userId, isLeader }}|void|Set a member of a space as a manager. You should use setManager(org.exoplatform.social.core.space.model.Space, String, boolean) instead. It will be removed in Social 1.3.x.| +|*setLeader*(String spaceId, String userId, boolean isLeader) throws SpaceException|{{spaceId, userId, isLeader}}|void|Set a member of a space as a manager. You should use setManager(org.exoplatform.social.core.space.model.Space, String, boolean) instead. It will be removed in Social 1.3.x.| +|*isLeader*(Space space, String userId) throws SpaceException|{{space, userId}}|boolean |Check whether a user is a space's leader or not. You should use isManager(org.exoplatform.social.core.space.model.Space, String) instead. It will be removed in Social 1.3.x.| +|*isLeader*(String spaceId, String userId) throws SpaceException|{{spaceId, userId}}|boolean |Check whether a user is a space's leader or not. You should use isManager(org.exoplatform.social.core.space.model.Space, String) instead. It will be removed in Social 1.3.x.| +|*isOnlyLeader*(Space space, String userId) throws SpaceException|{{space, userId}}|boolean|Check whether a user is the only leader of a space or not. You should use isOnlyManager(org.exoplatform.social.core.space.model.Space, String) instead. It will be removed in Social 1.3.x.| +|*isOnlyLeader*(String spaceId, String userId) throws SpaceException|{{spaceId, userId}}|boolean|Check whether a user is the only leader of a space or not. You should use isOnlyManager(org.exoplatform.social.core.space.model.Space, String) instead. It will be removed in Social 1.3.x.| +|*isMember*(String spaceId, String userId) throws SpaceException|{{spaceId, userId, }}| boolean |Check whether a user is a space's member or not. You should use isMember(org.exoplatform.social.core.space.model.Space, String) instead. It will be removed in Social 1.3.x.| +|*hasAccessPermission*(String spaceId, String userId) throws SpaceException|{{spaceId, userId}}|boolean |Check if a user can access a space or not. You should use hasAccessPermission(org.exoplatform.social.core.space.model.Space, String) instead. It will be removed in Social 1.3.x.| +|*hasEditPermission*(Space space, String userId) throws SpaceException|{{space, userId}}|Boolean |Check if a user can have the edit permission of a space or not. You should use hasSettingPermission(org.exoplatform.social.core.space.model.Space, String) instead. It will be removed in Social 1.3.x.| +|*hasEditPermission*(String spaceId, String userId) throws SpaceException|{{spaceId, userId}}|Boolean |Check if a user can have the edit permission of a space or not. You should use hasSettingPermission(org.exoplatform.social.core.space.model.Space, String) instead. It will be removed in Social 1.3.x.| +|*isInvited*(Space space, String userId) throws SpaceException|{{space, userId}}|Boolean |Check if a user is in the invited list of a space or not. You should use isInvitedUser(org.exoplatform.social.core.space.model.Space, String) instead. It will be removed in Social 1.3.x.| +|*isInvited*(String spaceId, String userId) throws SpaceException|{{spaceId, userId}}|Boolean |Check if a user is in the invited list of a space or not. You should use isInvitedUser(org.exoplatform.social.core.space.model.Space, String) instead. It will be removed in Social 1.3.x.| +|*isPending*(Space space, String userId) throws SpaceException|{{space, userId}}|Boolean |Check if a user is in the pending list of a space or not.You should use isPendingUser(org.exoplatform.social.core.space.model.Space, String) instead. It will be removed in Social 1.3.x.| +|*isPending*(String spaceId, String userId) throws SpaceException|{{spaceId, userId}}|Boolean | Check if a user is in the pending list of a space or not. You should use isPendingUser(org.exoplatform.social.core.space.model.Space, String) instead. It will be removed in Social 1.3.x.| |*installApplication*(String spaceId, String appId) throws SpaceException|{{spaceId, appId}}|void|Install an application to a space.| |*installApplication*(Space space, String appId) throws SpaceException|{{space, appId}}|void |Install an application to a space.| |*activateApplication*(Space space, String appId) throws SpaceException|{{space, appId}}| void|Activate an installed application in a space.| @@ -177,26 +177,26 @@ h1. SpaceService {anchor:id=Developer_document.JavaAPIs.Java_APIs.SpaceService} |*deactivateApplication*(String spaceId, String appId) throws SpaceException|{{spaceId, appId}}|void|Deactivate an installed application in a space.| |*removeApplication*(Space space, String appId, String appName) throws SpaceException|{{space, appId, appName}}| void|Remove an installed application from a space.| |*removeApplication*(String spaceId, String appId, String appName) throws SpaceException|{{space, appId, appName}}|void|Remove an installed application from a space.| -|*requestJoin*(Space space, String userId) throws SpaceException|{{space, userId}}| void |Request users to join a space. The invited users are then added to the pending list of the space. You should use addPendingUser(org.exoplatform.social.core.space.model.Space, String) instead. It will be removed in eXo Social 1.3.x.| -|*requestJoin*(String spaceId, String userId) throws SpaceException|{{spaceId, userId}}|void|Request users to join a space. The invited users are then added to the pending list of the space.. You should use addPendingUser(org.exoplatform.social.core.space.model.Space, String) instead. It will be removed in eXo Social 1.3.x.| -|*revokeRequestJoin*(Space space, String userId) throws SpaceException|{{space, userId}}|void|Revoke a join request after users request to join a group and is in the pending status. You should use removePendingUser(org.exoplatform.social.core.space.model.Space, String) instead. It will be removed in eXo Social 1.3.x.| -|*revokeRequestJoin*(String spaceId, String userId) throws SpaceException|{{spaceId, userId}}|void|Revoke a request to join a space. You should use removePendingUser(org.exoplatform.social.core.space.model.Space, String) instead. It will be removed in eXo Social 1.3.x.| -|*inviteMember*(Space space, String userId) throws SpaceException|{{space, userId}}| void |Invite a userId to become a member of a space. You should use addInvitedUser(org.exoplatform.social.core.space.model.Space, String) instead. It will be removed in eXo Social 1.3.x.| -|*inviteMember*(String spaceId, String userId) throws SpaceException|{{spaceId, userId}}|void|Invite a userId to a be member of a space. You should use addInvitedUser(org.exoplatform.social.core.space.model.Space, String) instead. It will be removed in eXo Social 1.3.x.| -|*revokeInvitation*(Space space, String userId) throws SpaceException|{{space, userId}}|void|Revoke an invitation. Remove a user from the invited member list of the space. You should use removeInvitedUser(org.exoplatform.social.core.space.model.Space, String) instead. It will be removed in eXo Social 1.3.x.| -|*revokeInvitation*(String spaceId, String userId) throws SpaceException|{{spaceId, userId}}|void|Revoke an invitation. Remove a user from the invited member list of the space. You should use removeInvitedUser(org.exoplatform.social.core.space.model.Space, String) instead. It will be removed in eXo Social 1.3.x.| -|*acceptInvitation*(Space space, String userId) throws SpaceException|{{space, userId}}|void|Accept an invitation and move a user from the invited list to the member list. You should use addMember(org.exoplatform.social.core.space.model.Space, String) instead. It will be removed in eXo Social 1.3.x.| -|*acceptInvitation*(String spaceId, String userId) throws SpaceException|{{spaceId, userId}}|void|Accept an invitation and move a user from the invited list to the member list. You should use addMember(org.exoplatform.social.core.space.model.Space, String) instead. It will be removed in eXo Social 1.3.x.| -|*denyInvitation*(Space space, String userId) throws SpaceException|{{space, userId}}|void|Deny an invitation and remove a user from the invited list. You should use removeInvitedUser(org.exoplatform.social.core.space.model.Space, String) instead. It will be removed in eXo Social 1.3.x.| -|*denyInvitation*(String spaceId, String userId) throws SpaceException|{{spaceId, userId}}|void|Deny an invitation and remove a user from the invited list. You should use removeInvitedUser(org.exoplatform.social.core.space.model.Space, String) instead. It will be removed in eXo Social 1.3.x.| -|*validateRequest*(Space space, String userId) throws SpaceException|{{space, userId}}|void|Validate a request and move a user from the pending list to the member list. You should use addMember(org.exoplatform.social.core.space.model.Space, String) instead. It will be removed in eXo Social 1.3.x.| -|*validateRequest*(String spaceId, String userId) throws SpaceException|{{spaceId, userId}}|void|Validate a request and move a user from the pending list to the member list. You should use addMember(org.exoplatform.social.core.space.model.Space, String) instead. It will be removed in eXo Social 1.3.x.| -|*declineRequest*(Space space, String userId) throws SpaceException|{{space, userId}}|void|Decline a request and remove a user from the pending list. You should use removePendingUser(org.exoplatform.social.core.space.model.Space, String) instead. It will be removed in eXo Social 1.3.x.| -|*declineRequest*(String spaceId, String userId) throws SpaceException|{{spaceId, userId}}|void|Decline a request and remove a user from the pending list. You should use removePendingUser(org.exoplatform.social.core.space.model.Space, String) instead. It will be removed in eXo Social 1.3.x.| -|*registerSpaceLifeCycleListener*(SpaceLifeCycleListener listener|{{listener}}|void|Register a space lifecycle listener. Deprecated: it will be removed in eXo Social 1.3.x.| -|*unregisterSpaceLifeCycleListener*(SpaceLifeCycleListener listener)|{{listener}}|void|Unregister a space lifecycle listener. Deprecated: it will be removed in eXo Social 1.3.x.| -|*setPortletsPrefsRequired*(PortletPreferenceRequiredPlugin portletPrefsRequiredPlugin)|{{portletPrefsRequiredPlugin}}|void| Set the portlet preferences got from the plug-in configuration. You should use SpaceApplicationConfigPlugin(org.exoplatform.social.core.space.model.Space, String) instead. It will be removed in eXo Social 1.3.x.| -|*getPortletsPrefsRequired*()|{{N/A}}|String|Get the portlet preferences required to use in creating the portlet application. Deprecated: it will be removed in eXo Social 1.3.x.| +|*requestJoin*(Space space, String userId) throws SpaceException|{{space, userId}}| void |Request users to join a space. The invited users are then added to the pending list of the space. You should use addPendingUser(org.exoplatform.social.core.space.model.Space, String) instead. It will be removed in Social 1.3.x.| +|*requestJoin*(String spaceId, String userId) throws SpaceException|{{spaceId, userId}}|void|Request users to join a space. The invited users are then added to the pending list of the space.. You should use addPendingUser(org.exoplatform.social.core.space.model.Space, String) instead. It will be removed in Social 1.3.x.| +|*revokeRequestJoin*(Space space, String userId) throws SpaceException|{{space, userId}}|void|Revoke a join request after users request to join a group and is in the pending status. You should use removePendingUser(org.exoplatform.social.core.space.model.Space, String) instead. It will be removed in Social 1.3.x.| +|*revokeRequestJoin*(String spaceId, String userId) throws SpaceException|{{spaceId, userId}}|void|Revoke a request to join a space. You should use removePendingUser(org.exoplatform.social.core.space.model.Space, String) instead. It will be removed in Social 1.3.x.| +|*inviteMember*(Space space, String userId) throws SpaceException|{{space, userId}}| void |Invite a userId to become a member of a space. You should use addInvitedUser(org.exoplatform.social.core.space.model.Space, String) instead. It will be removed in Social 1.3.x.| +|*inviteMember*(String spaceId, String userId) throws SpaceException|{{spaceId, userId}}|void|Invite a userId to a be member of a space. You should use addInvitedUser(org.exoplatform.social.core.space.model.Space, String) instead. It will be removed in Social 1.3.x.| +|*revokeInvitation*(Space space, String userId) throws SpaceException|{{space, userId}}|void|Revoke an invitation. Remove a user from the invited member list of the space. You should use removeInvitedUser(org.exoplatform.social.core.space.model.Space, String) instead. It will be removed in Social 1.3.x.| +|*revokeInvitation*(String spaceId, String userId) throws SpaceException|{{spaceId, userId}}|void|Revoke an invitation. Remove a user from the invited member list of the space. You should use removeInvitedUser(org.exoplatform.social.core.space.model.Space, String) instead. It will be removed in Social 1.3.x.| +|*acceptInvitation*(Space space, String userId) throws SpaceException|{{space, userId}}|void|Accept an invitation and move a user from the invited list to the member list. You should use addMember(org.exoplatform.social.core.space.model.Space, String) instead. It will be removed in Social 1.3.x.| +|*acceptInvitation*(String spaceId, String userId) throws SpaceException|{{spaceId, userId}}|void|Accept an invitation and move a user from the invited list to the member list. You should use addMember(org.exoplatform.social.core.space.model.Space, String) instead. It will be removed in Social 1.3.x.| +|*denyInvitation*(Space space, String userId) throws SpaceException|{{space, userId}}|void|Deny an invitation and remove a user from the invited list. You should use removeInvitedUser(org.exoplatform.social.core.space.model.Space, String) instead. It will be removed in Social 1.3.x.| +|*denyInvitation*(String spaceId, String userId) throws SpaceException|{{spaceId, userId}}|void|Deny an invitation and remove a user from the invited list. You should use removeInvitedUser(org.exoplatform.social.core.space.model.Space, String) instead. It will be removed in Social 1.3.x.| +|*validateRequest*(Space space, String userId) throws SpaceException|{{space, userId}}|void|Validate a request and move a user from the pending list to the member list. You should use addMember(org.exoplatform.social.core.space.model.Space, String) instead. It will be removed in Social 1.3.x.| +|*validateRequest*(String spaceId, String userId) throws SpaceException|{{spaceId, userId}}|void|Validate a request and move a user from the pending list to the member list. You should use addMember(org.exoplatform.social.core.space.model.Space, String) instead. It will be removed in Social 1.3.x.| +|*declineRequest*(Space space, String userId) throws SpaceException|{{space, userId}}|void|Decline a request and remove a user from the pending list. You should use removePendingUser(org.exoplatform.social.core.space.model.Space, String) instead. It will be removed in Social 1.3.x.| +|*declineRequest*(String spaceId, String userId) throws SpaceException|{{spaceId, userId}}|void|Decline a request and remove a user from the pending list. You should use removePendingUser(org.exoplatform.social.core.space.model.Space, String) instead. It will be removed in Social 1.3.x.| +|*registerSpaceLifeCycleListener*(SpaceLifeCycleListener listener|{{listener}}|void|Register a space lifecycle listener. Deprecated: it will be removed in Social 1.3.x.| +|*unregisterSpaceLifeCycleListener*(SpaceLifeCycleListener listener)|{{listener}}|void|Unregister a space lifecycle listener. Deprecated: it will be removed in Social 1.3.x.| +|*setPortletsPrefsRequired*(PortletPreferenceRequiredPlugin portletPrefsRequiredPlugin)|{{portletPrefsRequiredPlugin}}|void| Set the portlet preferences got from the plug-in configuration. You should use SpaceApplicationConfigPlugin(org.exoplatform.social.core.space.model.Space, String) instead. It will be removed in Social 1.3.x.| +|*getPortletsPrefsRequired*()|{{N/A}}|String|Get the portlet preferences required to use in creating the portlet application. Deprecated: it will be removed in Social 1.3.x.| diff --git a/docs/refguide/src/main/resources/wikbook/en/en-US/DeveloperReference/Overrideable_components.wiki b/docs/refguide/src/main/resources/wikbook/en/en-US/DeveloperReference/Overrideable_components.wiki index a99b7d0457..98df4ae07c 100644 --- a/docs/refguide/src/main/resources/wikbook/en/en-US/DeveloperReference/Overrideable_components.wiki +++ b/docs/refguide/src/main/resources/wikbook/en/en-US/DeveloperReference/Overrideable_components.wiki @@ -1,4 +1,4 @@ -There are 2 components in eXo Social that can be overridden: Space Application Handler & Space Service. +There are 2 components in Social that can be overridden: Space Application Handler & Space Service. * *Space Application Handler* {code:xml} diff --git a/docs/refguide/src/main/resources/wikbook/en/en-US/DeveloperReference/Production_Deployment_Tutorial.wiki b/docs/refguide/src/main/resources/wikbook/en/en-US/DeveloperReference/Production_Deployment_Tutorial.wiki index 2e7dad2e56..08e76b9b23 100644 --- a/docs/refguide/src/main/resources/wikbook/en/en-US/DeveloperReference/Production_Deployment_Tutorial.wiki +++ b/docs/refguide/src/main/resources/wikbook/en/en-US/DeveloperReference/Production_Deployment_Tutorial.wiki @@ -1,18 +1,18 @@ -h1. How to deploy eXo Social in Production {anchor:id=SOCref.DeveloperReference.how_to_deploy_eXo_Social_in_Production} +h1. How to deploy Social in Production {anchor:id=SOCref.DeveloperReference.how_to_deploy_eXo_Social_in_Production} h1. Objective {anchor:id=SOCref.DeveloperReference.Objective} -In this article, you will learn how to install eXo Social on a production server in a typical 3-tier architecture (web server / app server / database server). +In this article, you will learn how to install Social on a production server in a typical 3-tier architecture (web server / app server / database server). The case of the demo server at http://social.demo.exoplatform.org is used here. -This tutorial is intended for sysadmins. If you are a casual evaluator and just want to run eXo Social on your own computer, the [Quick Install Guide|InstallGuide] should be enough for you. +This tutorial is intended for sysadmins. If you are a casual evaluator and just want to run Social on your own computer, the [Quick Install Guide|InstallGuide] should be enough for you. h1. Requirements {anchor:id=SOCref.DeveloperReference.Requirements} This guide assumes that you have up and running apache and mysql instances and that you have basic knowledge on how to configure it. * [apache web server|http://www.apache.org] + mod_jk -* [eXo Social package|https//sourceforge:net-projects-exo-social-files-] properly [installed|InstallGuide] on a server with Java6. +* [Social package|https//sourceforge:net-projects-exo-social-files-] properly [installed|InstallGuide] on a server with Java6. * [mysql database server|http://www.mysql.org] and the corresponding [JDBC Driver|http://www.mysql.com/downloads/connector/j/] We assume that you have apache and mysql up and running and that you followed the steps of the [Quick Install Guide|InstallGuide] successfully. @@ -107,7 +107,7 @@ A dedicated schema is being used for the demo called _{{{demo_social}}}_. * then create the schema {code}create database demo_social default charset latin1 collate latin1_general_cs;{code} -h1. Configure eXo Social {anchor:id=SOCref.DeveloperReference.Configure_eXo_Social} +h1. Configure Social {anchor:id=SOCref.DeveloperReference.Configure_eXo_Social} * Drop your mysql jdbc jar driver in $SOCIAL_HOME/lib * Edit the database configuration in this file : $SOCIAL_HOME/gatein/conf/portal/socialdemo/socialdemo.properties {code:xml} diff --git a/docs/refguide/src/main/resources/wikbook/en/en-US/DeveloperReference/Rest_Service_APIs.wiki b/docs/refguide/src/main/resources/wikbook/en/en-US/DeveloperReference/Rest_Service_APIs.wiki index 29570d5645..faa4ecd780 100644 --- a/docs/refguide/src/main/resources/wikbook/en/en-US/DeveloperReference/Rest_Service_APIs.wiki +++ b/docs/refguide/src/main/resources/wikbook/en/en-US/DeveloperReference/Rest_Service_APIs.wiki @@ -1,6 +1,6 @@ *Objectives*: - The third parties want to integrate and extend the eXo Social capability and features and eXo Social REST Services APIs are dedicated for them to complete that. By using these REST APIs, the third parties can write any applications (desktop apps, mobile apps, web apps) to integrate with eXo Social services and business. + The third parties want to integrate and extend the Social capability and features and Social REST Services APIs are dedicated for them to complete that. By using these REST APIs, the third parties can write any applications (desktop apps, mobile apps, web apps) to integrate with Social services and business. *Conventions*: @@ -22,11 +22,11 @@ The JSON support is mandatory. The other format SHOULD be supported too (XML, RS The _rest\_context\_name_ and _portal\_container\_name_ parameters are used as follows: -* On eXo Social standalone: +* In Social standalone: ** _rest\_context\_name_: _rest-socialdemo_; ** _portal\_container\_name_: _socialdemo_; -* On eXo Platform: +* In eXo Platform: ** _rest\_context\_name_: _rest_; ** _portal\_container\_name_: _portal_; diff --git a/docs/refguide/src/main/resources/wikbook/en/en-US/DeveloperReference/Space_Portlet_Preference.wiki b/docs/refguide/src/main/resources/wikbook/en/en-US/DeveloperReference/Space_Portlet_Preference.wiki index 871aea5820..44be5cacb1 100644 --- a/docs/refguide/src/main/resources/wikbook/en/en-US/DeveloperReference/Space_Portlet_Preference.wiki +++ b/docs/refguide/src/main/resources/wikbook/en/en-US/DeveloperReference/Space_Portlet_Preference.wiki @@ -1,6 +1,6 @@ h1. Save and get space context from a portlet {anchor:id=SOCref.DeveloperReference.Save_and_get_space_context_from_a_portlet} {info} -Since eXo Social 1.0.1 +Since Social 1.0.1 {info} diff --git a/docs/refguide/src/main/resources/wikbook/en/en-US/DeveloperReference/XMLProcessor.wiki b/docs/refguide/src/main/resources/wikbook/en/en-US/DeveloperReference/XMLProcessor.wiki index c9dd8d3e1d..1f761017ba 100644 --- a/docs/refguide/src/main/resources/wikbook/en/en-US/DeveloperReference/XMLProcessor.wiki +++ b/docs/refguide/src/main/resources/wikbook/en/en-US/DeveloperReference/XMLProcessor.wiki @@ -39,7 +39,7 @@ XMLProcessor is initialized by IOC (Invesion of Control) via the configuration f {code} h1. Built-in XMLProcessor Plugins {anchor:id="SOCref_developreference_XMLProcessor_Plugins"} -In eXo Social, there are the following built-in XMLProcessor plugins (also known as *filters*) that filter the input texts of users. +In Social, there are the following built-in XMLProcessor plugins (also known as *filters*) that filter the input texts of users. || Filters || Description || |*DOMContentEscapeFilter*|Process the *DOM tree* input and escape all *text nodes*.| |*DOMLineBreakerFilter*|Process the *DOM tree* input and add
to all *text nodes* which contain {{{\\n}}}.| @@ -48,7 +48,7 @@ In eXo Social, there are the following built-in XMLProcessor plugins (also known |*XMLBalancer*|Process the String input and add missing close tags to input.| |*XMLTagFilter*|Process the String input and convert all tags which do not exist in the allowed tags list into the escapsed String.| -The following is the general Class diagram of XMLProcesscor in eXo Social: +The following is the general Class diagram of XMLProcesscor in Social: !images/ProcessorAndFilterClassDiagram.png|align="center" width="120mm" fo:scalefit="1" html:scalefit="0"! diff --git a/docs/refguide/src/main/resources/wikbook/en/en-US/DeveloperReference/widget_tutorial.wiki b/docs/refguide/src/main/resources/wikbook/en/en-US/DeveloperReference/widget_tutorial.wiki index 1d20ba36e2..e95622bd65 100644 --- a/docs/refguide/src/main/resources/wikbook/en/en-US/DeveloperReference/widget_tutorial.wiki +++ b/docs/refguide/src/main/resources/wikbook/en/en-US/DeveloperReference/widget_tutorial.wiki @@ -1,6 +1,6 @@ -The eXo Social widget enables developers to add capabilities of eXo Social to external applications. Since the widget is hosted on your eXo Social server, it can display personalized information. An activity stream of the most recent user actions will display to the group's members. +The Social widget enables developers to add capabilities of Social to external applications. Since the widget is hosted on your Social server, it can display personalized information. An activity stream of the most recent user actions will display to the group's members. -There are two options of the eXo Social widget that provide different levels of integration and information. +There are two options of the Social widget that provide different levels of integration and information. The basic version of this widget is an iFrame. The more advanced version is a button you can insert in a page; this will display a small pop-up with information about the space. @@ -14,8 +14,8 @@ spaceName=NAME_OF_YOUR_SPACE&description=DESCRIPTION_OF_THE_SPACE"> {code} To install this version in your application, replace all the uppercase text below: -* _{{{URL_OF_YOUR_EXO_INSTALLATION.COM}}}_: This is the URL of your eXo Social installation. If you are testing on your local computer, the URL may be _{{{localhost:8080}}}_. -* _{{{NAME_OF_YOUR_SPACE}}}_: This is the title of your space in eXo Social. In the URL, it is necessary to avoid special characters. For the space name, you can only use alphanumeric characters and {{{"_"}}}, ".", "-" or ".". +* _{{{URL_OF_YOUR_EXO_INSTALLATION.COM}}}_: This is the URL of your Social installation. If you are testing on your local computer, the URL may be _{{{localhost:8080}}}_. +* _{{{NAME_OF_YOUR_SPACE}}}_: This is the title of your space in Social. In the URL, it is necessary to avoid special characters. For the space name, you can only use alphanumeric characters and {{{"_"}}}, ".", "-" or ".". * _{{{DESCRIPTION_OF_THE_SPACE}}}_: This will be displayed in the list of spaces. h1. Advanced version {anchor:id=SOCref.DeveloperReference.widget_tutorial.advanced_version} diff --git a/docs/refguide/src/main/resources/wikbook/en/en-US/jcr_structure.wiki b/docs/refguide/src/main/resources/wikbook/en/en-US/jcr_structure.wiki index c377b6cc81..b1083d67b9 100644 --- a/docs/refguide/src/main/resources/wikbook/en/en-US/jcr_structure.wiki +++ b/docs/refguide/src/main/resources/wikbook/en/en-US/jcr_structure.wiki @@ -1,7 +1,7 @@ -Like any other eXo's products, eXo Social fully complies the JCR standard to store data (identity, profile, activity, space and relationship). -The eXo Social JCR structure is organized to conform to the data storage for the individual purpose of eXo Social. With this structure, it is easy for you to manage and access the data properly. +Like any other eXo's products, Social fully complies the JCR standard to store data (identity, profile, activity, space and relationship). +The Social JCR structure is organized to conform to the data storage for the individual purpose of Social. With this structure, it is easy for you to manage and access the data properly. -See the eXo Social JCR structure in the chart below: +See the Social JCR structure in the chart below: !images/Social-Workspace.png|align="center" width="150mm" fo:scalefit="1" html:scalefit="0"! @@ -9,8 +9,8 @@ See the eXo Social JCR structure in the chart below: The root node of Social workspace is _/production/_ which consists of two child nodes named _{{{soc:providers}}}_, and _{{{soc:spaces}}}_. h1. soc:providers {anchor:id=SOCref.Social_JCR_Structure.socproviders} -The _{{{soc:providers}}}_ node is used to store the provider entities. In eXo Social, there are two built-in provider entities, including _organization_, and _space_. -Its type is _{{{soc:providers}}}_ that has the _soc\:_ child node of the _{{{soc:providerdefinition}}}_ type. +The _soc\:providers_ node is used to store the provider entities. In Social, there are two built-in provider entities, including _organization_, and _space_. +Its type is _soc\:providers_ that has the _soc\:_ child node of the _soc\:providerdefinition_ type. {docbook} @@ -22,9 +22,9 @@ soc:]]> {docbook} -The parameter in the _{{{soc\:}}}_ node depends on the identity providers. eXo Social has two identity providers, including _OrgarnizationIdentityProvider_, and _SpaceIdentityProvider_ that contain organization identities (users) and space identities respectively. +The __ parameter in the _soc\:_ node depends on the identity providers. Social has two identity providers, including _OrgarnizationIdentityProvider_, and _SpaceIdentityProvider_ that contain organization identities (users) and space identities respectively. -The _{{{soc:}}}_ node of the _{{{soc:providerdefinition}}}_ type has the _{{{soc:}}}_ child nodes that have the _{{{soc:identitydefinition}}}_ type. +The _soc\:_ node of the _soc\:providerdefinition_ type has the _soc\:_ child nodes that have the _soc\:identitydefinition_ type. h1. Identity {anchor:id=SOCref.Social_JCR_Structure.IdentityEntity} {include:document="chromattic/generated/org.exoplatform.social.core.chromattic.entity.IdentityEntity.wiki"} @@ -35,7 +35,7 @@ h1. Relationship {anchor:id=SOCref.Social_JCR_Structure.RelationshipEntity} h1. Profile {anchor:id=SOCref.Social_JCR_Structure.ProfileEntity} {include:document="chromattic/generated/org.exoplatform.social.core.chromattic.entity.ProfileEntity.wiki"} -Some residual properties can be set and will be used by eXo Social : +Some residual properties can be set and will be used by Social: || Property Name || Required Type || Multiple|| Description || |void-Url|undefined | true| The URL to access the profile of an identity.| |void-email|undefined | true| The email of an identity in the profile. | @@ -66,7 +66,7 @@ h1. Activity parameters {anchor:id=SOCref.Social_JCR_Structure.ActivityParameter The _{{{soc:activityparam}}}_ node type has the following property: || Property Name || Required Type || Multiple|| Description || -|*|String|false|A map of key-values. | +|\*|String|false|A map of key-values. | h1. Space list {anchor:id=SOCref.Social_JCR_Structure.SpaceListEntity} {include:document="chromattic/generated/org.exoplatform.social.core.chromattic.entity.SpaceListEntity.wiki"}