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

NoClassDefFound jakarta/servlet/ServletConnection #29473

Closed
hantsy opened this issue Nov 12, 2022 · 3 comments
Closed

NoClassDefFound jakarta/servlet/ServletConnection #29473

hantsy opened this issue Nov 12, 2022 · 3 comments
Labels
for: stackoverflow A question that's better suited to stackoverflow.com status: invalid An issue that we don't feel is valid

Comments

@hantsy
Copy link
Contributor

hantsy commented Nov 12, 2022 •
edited

Affects: Spring Framework 6.0.0-RC4

I upgraded my example projects from Spring 6.0.0-RC2 to Spring 6.0.0-RC4, it fails my controller tests.

NoClassDefFound jakarta/servlet/ServletConnection

The complete log stack: https://github.com/hantsy/spring6-sandbox/actions/runs/3449289782/jobs/5757083220

It seems the spring-webmvc and spring-test removes the dependency of jakarta.servlet, etc?
@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged or decided on label Nov 12, 2022
@bclozel
Copy link
Member

bclozel commented Nov 12, 2022

Our Servlet mocks require Servlet 6.0 now. See https://github.com/spring-projects/spring-framework/wiki/What%27s-New-in-Spring-Framework-6.x#testing and #29435

@bclozel bclozel closed this as not planned Won't fix, can't repro, duplicate, stale Nov 12, 2022
@bclozel bclozel added status: invalid An issue that we don't feel is valid for: stackoverflow A question that's better suited to stackoverflow.com and removed status: waiting-for-triage An issue we've not yet triaged or decided on labels Nov 12, 2022
@hantsy
Copy link
Contributor Author

hantsy commented Nov 12, 2022 •
edited

OK, upgraded to Jakarta EE 10 APIs, it is simply resolved.

@ratoaq2
Copy link

ratoaq2 commented Feb 25, 2023

Spring 6 supports Jetty 11, which requires Servlet 5.0.
But now servlet mock requires Servlet 6.0.

Currently, either I use servlet 5.0 for my application to start, or servlet 6.0 to run the tests with servlet mock

@bclozel bclozel mentioned this issue Jun 9, 2023
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
for: stackoverflow A question that's better suited to stackoverflow.com status: invalid An issue that we don't feel is valid
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@bclozel @hantsy @ratoaq2 @spring-projects-issues