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

Issue #6287 - fix classloading for WebSocketClient in webapp #6293

Merged

Conversation

lachlan-roberts
Copy link
Contributor

Issue #6287

Signed-off-by: Lachlan Roberts <lachlan@webtide.com>
Copy link
Contributor

@sbordet sbordet left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would like to see a similar test for Jetty's API as well.
I know the fix is in core, but we want to make sure.

Signed-off-by: Lachlan Roberts <lachlan@webtide.com>
@sbordet
Copy link
Contributor

sbordet commented May 19, 2021

@lachlan-roberts apparently the tests you added for this issue fail, can you check?

@lachlan-roberts lachlan-roberts added this to In progress in Jetty 10.0.3/11.0.3 via automation May 19, 2021
Signed-off-by: Lachlan Roberts <lachlan@webtide.com>
Jetty 10.0.3/11.0.3 automation moved this from In progress to Reviewer approved May 19, 2021
@lachlan-roberts lachlan-roberts merged commit 455e798 into jetty-10.0.x May 20, 2021
Jetty 10.0.3/11.0.3 automation moved this from Reviewer approved to Done May 20, 2021
@lachlan-roberts lachlan-roberts deleted the jetty-10.0.x-6287-WebSocketClientClassLoading branch May 20, 2021 07:55
@sbordet sbordet linked an issue May 25, 2021 that may be closed by this pull request
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
Development

Successfully merging this pull request may close these issues.

Class loading broken for WebSocketClient used inside webapp
2 participants