Getting Started with Topic API
This tutorial shows how to use the low-level Collaboration Kit APIs, by updating and subscribing to a topic map.
To be more productive in creating collaborative applications, use the high-level APIs as described in the Quick Start Guide.
Preparations
Follow the preparation steps in the Preparing the Application in the Quick Start Guide.
Add Collaboration Features
This tutorial shows how to build a view with a checkbox where the user can choose whether they’re in a Friday mood.
Create a Simple View
First, create the view with a checkbox, but not any collaborative functionality — at least not yet.
Source code
TopicView.java
Define Topic Connection
Sharing data between multiple users happens through a TopicConnection instance. By default, the connection is deactivated until its related component is attached to the UI.
Open a connection to the tutorial topic, and define the activation callback which is triggered when the current TopicView component (i.e., this) is attached. The user who is related to the topic connection must be defined.
Source code
TopicView.java
The activation callback should return a registration, which Collaboration Kit runs when the connection is deactivated. Since the example does not yet register any listeners that need clean-up, it can return null.
Define Topic Category
The topic stores collaborative data in named maps and lists.
In the activation callback, get a map by its name:
Source code
TopicView.java
Pass Values to Topic
The first actual step to making the application collaborative is to update the topic whenever the checkbox value changes. The key isFriday is associated with the value of the checkbox. Add a value change listener that updates the related topic map.
Source code
TopicView.java
The topic’s structure now looks as follows:
Source code
Topic maps
|_ fieldValues
|_ isFriday: true/false|
Tip
|
Add Scope to Topic Data
By default, values are stored in the Topic until explicitly removed. You can use methods accepting a scope parameter and use EntryScope.CONNECTION to have the entry removed when the connection is deactivated.
|
Subscribe to Topic Changes
The final part of the code is to subscribe to updates to the topic map, and to update the checkbox if the related map is changed. This is also done in the activation callback so that the subscription is opened only when the view is actually used.
It’s also necessary to return the registration of the listener so it can be removed when the component is detached to avoid leaking memory.
Source code
TopicView.java
|
Tip
|
Combining Registrations
In case there are many registrations, they can be combined by Registration.combine(registration1, registration2);.
|
Run the Application
Follow the instructions in the application’s README.md file to start the application. Then open http://localhost:8080/ in multiple browser tabs to see how a change made in one tab is automatically shown in the other tabs.
D24BC999-9D07-4390-BC29-F57C87DBA927