Santiago Pericas-Geertsen

@mkarg I don't understand your question. This issue is really about implementation jars.

@asoldano No, we shouldn't do that. I've been told that, technically, splitting implementation jars was not allowed under the JCP rules (not sure where that's stated to be honest). Less...

@chkal I wouldn't think we need to go that far. Seems to me that it is sufficient to introduce this notion of supported configurations.

@jim-krueger Not a significant impact, other than maybe some text in the spec describing their benefits. There are a few features in Jakarta REST around async/reactive that become far less...

I agree, I don’t see the value of restricting it at the API level.

> Off-Topic: Just tried Jersey 2.32, and this _does not_ switch off the exception! Maybe a bug in Jersey not allowing to _override_ properties at that late point? > >...

I don't know the history of that, unfortunately. They are a bit odd for sure. We should definitely review this in the next major release.

> SseBroadcaster.onClose() has this description: > > ``` > /** > * Register a listener, which will be called when the SSE event output has been closed (either by client...

> > Are you asking whether this `onClose(Consumer onClose)` method makes any sense at all? > > I don't get In which case we need this api to listen SseEventSink's...

@jimma Are you asking as a JAX-RS developer or implementor? As a developer, you just get informed about the event, so it's up to you to do something with that...