You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* You can use `mvn -U org.codehaus.mojo:versions-maven-plugin:display-dependency-updates` to search for dependency
218
218
updates
219
219
220
+
#### SSE streams
221
+
222
+
We have 2 SSE streams available, one in the admin API at: `api/admin/events/{clientId}` and one in the viewer API
223
+
at: `api/events/{clientId}`. When using these streams you must make sure that you are using/injecting the correct
224
+
`SseEventBus` for each API.
225
+
226
+
For the admin use the default `eventBus` bean, inject using: `SseEventBus eventBus` (defined using the `@EnableSseEventBus` annotation in the `TailormapConfig` class).
227
+
for the viewer use the `viewerSseEventBus` bean, inject using: `@Qualifier("viewerSseEventBus") SseEventBus eventBus` (defined in the `TailormapConfig` class).
228
+
See:
229
+
-[ServerSentEventsAdminController](src/main/java/org/tailormap/api/controller/admin/ServerSentEventsAdminController.java) for the admin configuration
230
+
-[ServerSentEventsController](src/main/java/org/tailormap/api/controller/ServerSentEventsController.java) for the viewer configuration
231
+
-[TailormapConfig](src/main/java/org/tailormap/api/configuration/TailormapConfig.java) for the bean definitions
232
+
233
+
If you inject the wrong one you may not receive the events ypu want and ypu risk sending administrative events to the viewer.
0 commit comments