commit 0de816836cd1057f623578b0dd4b5632a9054ed8
author Andy McCright <j.andrew.mccright@gmail.com> Mon Aug 09 13:27:14 2021 -0500
committer GitHub <noreply@github.com> Mon Aug 09 13:27:14 2021 -0500
tree 4aeaef9410e4f5a18cd588260bd82189a86e7b3e
parent a8a65cecb681d32d5be50da170902c35c16a5407
parent 8795695d0e956efed17f56aebd588c3d4409ce10

Merge pull request #995 from NicoNes/ISSUE-992

Clarify behavior when SseEvent source onEvent throws and exception

jaxrs-api/src/main/java/jakarta/ws/rs/sse/SseEventSource.java

diff --git a/jaxrs-api/src/main/java/jakarta/ws/rs/sse/SseEventSource.java b/jaxrs-api/src/main/java/jakarta/ws/rs/sse/SseEventSource.java
index bc5f06d..56bd284 100644
--- a/jaxrs-api/src/main/java/jakarta/ws/rs/sse/SseEventSource.java
+++ b/jaxrs-api/src/main/java/jakarta/ws/rs/sse/SseEventSource.java
@@ -72,6 +72,11 @@
  * <p>
  * In the case of an error condition response, the <code>Throwable</code> passed to the <code>onError</code> consumer
  * <i>should</i> be a WebApplicationException containing the invalid <code>Response</code> object.
+ * <p>
+ * Note that if, for any of the registered event consumers, an invocation of {@link Consumer#accept(Object)
+ * Consumer&lt;InboundSseEvent&gt;#accept(InboundSseEvent)} method throws an exception, this is not an error condition.
+ * Thus <code>onError</code> is not invoked and event processing is not stopped.
+ * Users are encouraged to handle exceptions on their own as part of the event processing logic.
  *
  * @author Marek Potociar
  * @since 2.1