Skip to content

Update ServletContainerInitializer filename with old javax prefix to jakarta. #27690

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

Closed
marcusdacoregio opened this issue Nov 16, 2021 · 0 comments
Assignees
Labels
in: web Issues in web modules (web, webmvc, webflux, websocket) type: task A general task
Milestone

Comments

@marcusdacoregio
Copy link
Contributor

Affects: 6.0.0-SNAPSHOT

When implementing the WebApplicationInitializer interface, the implementation is never called.
This was caused because this file is still named with the old javax namespace.

As a workaround, I just added the file with the jakarta.servlet.ServletContainerInitializer to my app.

Found that problem while working with Spring Security samples that use the custom WebApplicationInitializer implementation.

@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged or decided on label Nov 16, 2021
@jhoeller jhoeller added in: web Issues in web modules (web, webmvc, webflux, websocket) type: task A general task and removed status: waiting-for-triage An issue we've not yet triaged or decided on labels Nov 16, 2021
@jhoeller jhoeller added this to the 6.0 M1 milestone Nov 16, 2021
@jhoeller jhoeller self-assigned this Nov 16, 2021
@jhoeller jhoeller changed the title Update filename with old javax prefix to jakarta. Update ServletContainerInitializer filename with old javax prefix to jakarta. Nov 16, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: web Issues in web modules (web, webmvc, webflux, websocket) type: task A general task
Projects
None yet
Development

No branches or pull requests

3 participants