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.

Sign up for GitHub

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

Jump to bottom

ClassNotFoundException using Jetty 10 and its reactive client #27112

Closed
urferr opened this issue Jun 30, 2021 · 0 comments
Closed

ClassNotFoundException using Jetty 10 and its reactive client #27112

urferr opened this issue Jun 30, 2021 · 0 comments
Assignees
@poutsma
Labels
in: web Issues in web modules (web, webmvc, webflux, websocket) type: enhancement A general enhancement
Milestone
5.3.9

Comments

@urferr
Copy link

urferr commented Jun 30, 2021

Affects: Spring Boot 2.5.2, Spring Framework 5.3.8, Jetty 10.0.5 and Jetty Reactive Client 2.0.3

I tried to use Jetty 10 together with latest Spring Boot/Framework. Unfortunately i run into a ClassNotFoundException in the method org.springframework.http.client.reactive.JettyClientHttpRequest.writeWith because in Jetty Reactive Client 2 the class PublisherContentProvider which is instantiated there does not exist anymore. Most probably now the new class PublisherRequestContent which is quite similar should be used
@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged or decided on label Jun 30, 2021
@poutsma poutsma added the in: web Issues in web modules (web, webmvc, webflux, websocket) label Jul 1, 2021
@poutsma poutsma self-assigned this Jul 1, 2021
@poutsma poutsma added this to the 5.3.9 milestone Jul 2, 2021
@poutsma poutsma closed this as completed in cb25134 Jul 6, 2021
@poutsma poutsma added type: enhancement A general enhancement and removed status: waiting-for-triage An issue we've not yet triaged or decided on labels Jul 6, 2021
poutsma added a commit that referenced this issue Jul 9, 2021
@poutsma
Reinstate abortOnCancel in JettyClientHttpRequest
297880d 
This commit reinstates abortOnCancel in the ReactiveRequest builder,
which allows a cancel signal to abort the request.

See gh-26287 and gh-27112
@sync-by-unito sync-by-unito bot mentioned this issue Jul 14, 2021
Merged
lxbzmy pushed a commit to lxbzmy/spring-framework that referenced this issue Mar 26, 2022
@poutsma @lxbzmy
Do not use internal API in JettyClientHttpConnector
acde7b7 
This commit makes sure that we no longer use the internal API in the
Jetty support for the WebClient. With this change, we are able to
support both Jetty 9, 10, and 11.

Closes spring-projectsgh-27112
lxbzmy pushed a commit to lxbzmy/spring-framework that referenced this issue Mar 26, 2022
@poutsma @lxbzmy
Reinstate abortOnCancel in JettyClientHttpRequest
805385f 
This commit reinstates abortOnCancel in the ReactiveRequest builder,
which allows a cancel signal to abort the request.

See spring-projectsgh-26287 and spring-projectsgh-27112
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@poutsma poutsma

Labels
in: web Issues in web modules (web, webmvc, webflux, websocket) type: enhancement A general enhancement
Projects
None yet
Milestone
5.3.9
Development

No branches or pull requests
3 participants
@poutsma @urferr @spring-projects-issues