-
Notifications
You must be signed in to change notification settings - Fork 39
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
Library does not work with recent Servlet containers #111
Comments
👋 Thanks for raising @uap-universe! I agree that a new major should be made available, which would (among other things) target Jakarta EE (will need to decide which version to target, likely 9.1). We do have plans for a new major version; it will likely be 2023 as first we are going to make a new major of |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you have not received a response for our team (apologies for the delay) and this is still a blocker, please reply with additional information or just a ping. Thank you for your contribution! 🙇♂️ |
Also chiming in requesting support for the new version(s) of the Java servlet spec, specifically 5.0 which changes javax.servlet.* to jakarta.servlet.*. |
We also require support for the updated servlet spec - any update on this? |
Also would like this as well. Even just s/javax/jakarta :) |
Any update for this? Need this in order to use with tomcat 10 |
Any update ? |
Still nothing? |
@jimmyjames This issue is now well over a year old, are there any updates on a timeline here? It's starting to be a blocking dependency to upgrading other projects to LTS versions |
It's over four years now, that Jakarta EE has been released, if I might add. The first versions of Tomcat that migrated to Jakarta EE are already end of life. |
@jimmyjames any updates as we enter the second quarter of 2024? If the update is "we're not going to maintain this anymore, please move on", can you please just let us know so we can figure out another solution? |
I guess we have to move on? Folks have you figured out a way to handle this ? I was thinking to make an adapter. |
Honestly, don't bother. This library is dead. I ended up writing my own implementation for the REST API methods I needed, and it works just fine. auth0 should pull this library to stop wasting people's time. |
Yes, I removed it - and the entire Okta SSO solution - from my application. But I see this is not an easy step for everyone. |
Describe the problem you'd like to have solved
The library does not work with recent Servlet containers that implement Jakarta EE.
Describe the ideal solution
A new major version of this library should be made available, that depends on jakarta.servlet instead of javax.servlet.
Whoever wants to use Java EE Servlet containers, can rely on the current major version of this library.
Alternatives and current work-arounds
Currently there does not seem to be an alternative in the com.auth0 group that could be used as a replacement for this library.
Additional information, if any
Jakarta EE was released more than two years ago and is broadly adopted.
Relates to #97
The text was updated successfully, but these errors were encountered: