The standard CUBA Events interface allows you to publish events that can be received by subscribers within the same application block. So there are no built-in facilities for notifying clients from middleware or propagating events in the cluster.
The Global Events add-on enables receiving Spring's application events on any application block of the distributed system. In the simplest configuration with core and web blocks running in a single JVM, it allows you to send events from core to web to notify UI screens or managed beans. In a cluster environment, an event published inside a block, will be received on all other connected parts of the system: on all middleware blocks and on the clients: web and portal.
In case of the client is deployed in the same JVM as middleware and cuba.useLocalServiceInvocation application property is set to true, it registers a callback in the LocalRegistry class located in the shared-lib module which is accessible to both middleware and the client.
In a distributed environment, clients open WebSocket connections to the middleware blocks, and middleware exchange events in a usual way using the cluster communication mechanism.
The add-on can be added to your project in one of the ways described below. Installation from the Marketplace is the simplest way. The last version of the add-on compatible with the used version of the platform will be installed. Also, you can install the add-on by coordinates choosing the required version of the add-on from the table.
In case you want to install the add-on by manual editing or by building from sources see the complete add-ons installation guide in CUBA Platform documentation.
- Open your application in CUBA Studio. Check the latest version of CUBA Studio on the CUBA Platform site.
- Go to CUBA -> Marketplace in the main menu.
- Find the Global Events add-on there.
- Click Install and apply the changes. The add-on corresponding to the used platform version will be installed.
- Open your application in CUBA Studio. Check the latest version of CUBA Studio on the CUBA Platform site.
- Go to CUBA -> Marketplace in the main menu.
- Click the icon in the upper-right corner.
- Paste the add-on coordinates in the corresponding field as follows:
com.haulmont.addon.globalevents:cubaglevt-global:<add-on version>
where <add-on version> is compatible with the used version of the CUBA platform.
| Platform Version | Add-on Version |
|---|---|
| 7.2.x | 0.6.1 |
| 7.1.x | 0.5.1 |
| 7.0.x | 0.4.2 |
| 6.10.x | 0.3.1 |
| 6.9.x | 0.2.1 |
| 6.8.x | 0.1.2 |
- Click Install and apply the changes. The add-on will be installed to your project.
Your global event classes must be inherited from com.haulmont.addon.globalevents.GlobalApplicationEvent, for example:
package com.company.sample;
import com.haulmont.addon.globalevents.GlobalApplicationEvent;
public class MyGlobalEvent extends GlobalApplicationEvent {
private String payload;
public MyGlobalEvent(Object source, String payload) {
super(source);
this.payload = payload;
}
public String getPayload() {
return payload;
}
}Make sure all fields of the event class are serializable! Also, do not ever use the source field to store and transfer any data, as it is transient and will not be preserved when the event is sent to another application block.
If you want to send event to Generic UI screens of connected web blocks, add the GlobalUiEvent marker interface to the event class:
package com.company.sample;
import com.haulmont.addon.globalevents.GlobalApplicationEvent;
import com.haulmont.addon.globalevents.GlobalUiEvent;
public class MyUiNotificationEvent extends GlobalApplicationEvent implements GlobalUiEvent {
private String message;
public MyUiNotificationEvent(Object source, String message) {
super(source);
this.message = message;
}
public String getMessage() {
return message;
}
}Send global events using the standard Events.publish() method, and they will be received by subscribers running on all blocks of your distributed application.
In the distributed deployment, it is recommended to suppress DEBUG log messages from WebSocketDispatcherServlet by adding the following line to logback.xml:
<logger name="com.haulmont.addon.globalevents.core.WebSocketDispatcherServlet" level="INFO"/>
-
Events are delivered to other blocks asynchronously, including the local deployment.
-
Ordering is accurate only within a block.
-
Delivery in a distributed deployment is guaranteed "at most once", i.e. there is no retransmit, etc.
-
In the distributed deployment, web client opens WebSocket connection to middleware on the first browser connection. So if some
webbean is subscribed to a global event, it will start to receive notifications only after at least one user connects to it.
The global-events-demo project contains usage examples and automatic system tests.
- If messages are not received and you see in the logs the message like this:
The decoded text message was too big for the output buffer and the endpoint does not support partial messages, see this topic for the solution.
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent