Mark Thomas
Mark Thomas
So, given the above discussions, are there any objections to proceeding with a 2.1.1 release (Jakarta EE 10) that includes this fix so the WebSocket 2.1.1 API works when running...
2.1.1 released
I hadn't thought of it from that perspective. The current wording means that back-pressure is provided by throwing an IllegalStateException for `Basic` which seems wrong to me. It also suggests...
See also #255 and #218
They way to do things like that is to map the server endpoint using a URI-template and use the `@PathParam` annotation.
`stream()` loads the class but does not instantiate an instance of the provider. Usage something like: ``` WebSocketContainer result = null; ServiceLoader loader = ServiceLoader.load(ContainerProvider.class); Stream stream = loader.stream(); Iterator...
Confirming as WONTFIX since SecurityManager support is being removed across the Jakarta EE platform.
I think it would be useful to get @rmannibucau 's view on this since the requirement originated with TomEE. My impression is that Predicate seems unnecessarily restrictive. It may work...
The `@Priority` solution seems very geared to the TomEE use case where there is a requirement to override an implementation in a dependency with a local implementation. It works because...
Clarification is (potentially) a change in behaviour so this will need to wait for Jakarta EE 10. As a note to self I don't think the API will need to...