![\"1-Activity-Stream\"](\"\/blog\/wp-content\/uploads\/2014\/04\/1-Activity-Stream.png\")
<\/a><\/p>\nIn some cases, you might want to remove such default activities from AS or implement customized actions based on dedicated activities. In this tutorial, you will see how to remove the activities for space leaving and space joining by overriding the SpaceActivityPublisher<\/b> listener.<\/p>\nHow a listener works<\/h2>\n
Listeners are registered with the main services. Every time the main service is running and fires a registered event, listeners will be called.<\/p>\n
<component>\n\t<key>org.exoplatform.social.core.space.spi.SpaceService<\/key>\n\t<type>org.exoplatform.social.core.space.impl.SpaceServiceImpl<\/type>\t\n\u2026\u2026\u2026\u2026\u2026\u2026 \t\n \t<component-plugin>\n \t\t<name>SpaceActivityPublisher<\/name>\n \t\t<set-method>addSpaceListener<\/set-method>\n \t\t<type>org.exoplatform.social.core.application.SpaceActivityPublisher<\/type>\n \t<\/component-plugin> \t\t\n\u2026\u2026\u2026\u2026\u2026\u2026\n <\/component><\/pre>\nThe above configuration can be found in social-extension.war<\/b>: \/WEB-INF\/conf\/social-extension\/social\/core-configuration.xml<\/span><\/p>\n
SpaceActivityPublisher<\/b> implements the SpaceLifeCycleListener<\/b> interface and it is registered with SpaceService <\/b>as a listener. It listens to most space-related activities, such as when a space is created, a space is removed, space settings change or someone leaves or joins a space, and it publishes them as social activities on AS.<\/p>\n
If you would like to remove all space-related activities from AS, just simply comment out the component plugin config of SpaceActivityPublisher<\/b>. This will disable the SpaceActivityPublisher<\/b> listener. If you want to remove just the activities for when someone leaves or joins a space, as seeing such activities can sometimes be annoying, then you have to override SpaceActivityPublisher<\/b> with your own implementation. To do so, you need to create an extension project, which can override the default components or default configuration of eXo Platform. Please find details for how to create an extension project here<\/a>.<\/p>\n
Override a listener<\/h2>\n
We will create a sub-class of SpaceActivityPublisher<\/b> called CustomSpaceActivityPublisher<\/b> in our extension project. In this class, we inherit all the methods of SpaceActivityPublisher<\/b>, and only override the joined(SpaceLifeCycleEvent event)<\/i> and left(SpaceLifeCycleEvent event)<\/i> methods so that no action is taken for the events when a member joins or leaves.<\/p>\n
public class CustomSpaceActivityPublisher extends SpaceActivityPublisher {\n public CustomSpaceActivityPublisher(InitParams params,\n \tActivityManager activityManager, IdentityManager identityManager) {\n\tsuper(params, activityManager, identityManager);\n\t\/\/ TODO Auto-generated constructor stub\n }\n\n \/**\n * {@inheritDoc}\n *\/\n @Override\n public void joined(SpaceLifeCycleEvent event) {\n \/\/Do nothing\n }\n\n \/**\n * {@inheritDoc}\n *\/\n @Override\n public void left(SpaceLifeCycleEvent event) {\n\t\/\/Do nothing\n }\n}<\/pre>\nOverride a configuration<\/h2>\n
As mentioned above, the configuration needed to register SpaceActivityPublisher<\/b> listener with SpaceService<\/b> is in social-extension.war:<\/b> \/WEB-INF\/conf\/social-extension\/social\/core-configuration.xml<\/span><\/p>\n
We copy this configuration file into our extension project and update the configuration as follows:<\/p>\n
<component-plugin>\n\t<name>SpaceActivityPublisher<\/name>\n\t<set-method>addSpaceListener<\/set-method>\n\t<type>org.exoplatform.customization.listener.CustomSpaceActivityPublisher<\/type>\n<\/component-plugin><\/pre>\nThis registers our new sub-class as the listener for SpaceService<\/b>. Remember that to override the existing core-configuration.xml<\/b> of social-extension.war<\/b>, we have to put our configuration file in the same path as the original one.<\/p>\n
* Important note:<\/i><\/b> We cannot just add the above listener registration to the existing core-configuration.xml<\/b>. We have to override the existing core-configuration.xml<\/b> with the new one in our extension project. This is to avoid a registration conflict.<\/i><\/p>\n
Launching customization<\/h2>\n
Now you are ready to deploy your extension project. The source code of a sample extension project can be found here<\/a>. After you have built this extension project using Maven, simply copy the .war files to $TomcatHome\/webapps<\/span> and copy the .jar files to $TomcatHome\/lib<\/span> then start your Tomcat instance.<\/p>\n
Going further<\/h2>\n
Customization can do more than removing unwanted activities from AS. You can override any method of the existing listener for the expected behavior. Besides SpaceActivityPublisher<\/b>, there are a number of overridable components<\/a> supported by eXo Platform.<\/p>\n
You can download the Sample extension project<\/a>.<\/p>\n