Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support ExecuteOn annotation with ServerWebSocket #10772

Merged
merged 4 commits into from
May 2, 2024

Conversation

jeremyg484
Copy link
Contributor

NettyServerWebSocketHandler is updated to check for the ExecuteOn
annotation when invoking any of the callback methods on a
ServerWebSocket annotated class, and to use the specified
ExecutorService when invoking the methods.

A test is added to verify the enhanced behavior.

This resolves #10758

NettyServerWebSocketHandler is updated to check for the ExecuteOn
annotation when invoking any of the callback methods on a
ServerWebSocket annotated class, and to use the specified
ExecutorService when invoking the methods.

A test is added to verify the enhanced behavior.

This resolves #10758
@jeremyg484 jeremyg484 requested a review from yawkat April 27, 2024 22:00
@sdelamo sdelamo added the type: improvement A minor improvement to an existing feature label Apr 29, 2024
@jeremyg484 jeremyg484 changed the title Support ExecutOn annotation with ServerWebSocket Support ExecuteOn annotation with ServerWebSocket Apr 30, 2024
@jeremyg484 jeremyg484 requested a review from yawkat May 2, 2024 02:42
Copy link

sonarqubecloud bot commented May 2, 2024

@jeremyg484 jeremyg484 merged commit 86914a7 into 4.5.x May 2, 2024
17 checks passed
@jeremyg484 jeremyg484 deleted the websocket-execute-on-45x branch May 2, 2024 20:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: improvement A minor improvement to an existing feature
Projects
No open projects
Status: Done
Development

Successfully merging this pull request may close these issues.

@ExecuteOn(TaskExecutors.IO) does not work with @ServerWebSocket
3 participants