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

Dropbox SDK updates to support certificate changes #544

Open
relvira0403 opened this issue Jun 27, 2024 · 1 comment
Open

Dropbox SDK updates to support certificate changes #544

relvira0403 opened this issue Jun 27, 2024 · 1 comment

Comments

@relvira0403
Copy link

We have received this notification sent Thursday, June 27, 2024 4:01 AM.

We tried updating the DropBox Java SDK version from v3.1.0 to v6.0.0 as specified in the email and it resulted to these exceptions.

  • The project was not built since its build path is incomplete. Cannot find the class file for jakarta.servlet.http.HttpSession. Fix the build path then try building this project web Unknown Java Problem
  • The type jakarta.servlet.http.HttpSession cannot be resolved. It is indirectly referenced from required .class files

Environment:
Java 11- Open Jdk-11.0.15.10-hotspot
SpringBoot - 2.3.0.RELEASE

We tried migrating javax.servlet.http.HttpSession; to jakarta.servlet.http.HttpSession as mentioned on this release below:

#495
https://github.com/dropbox/dropbox-sdk-java/blob/main/core/src/main/java/com/dropbox/core/DbxStandardSessionStore.java

Doing the changes above escalate to more complicated issues.

  1. All methods that uses javax.servlet.http.* are affected ex. HttpServletRequest, HttpServletResponse.
  2. Other integration services that uses javax.servlet.http.* were also affected e.g. Google Drive, One Drive and other Cloud Storage Integration Services.
  3. Mixing javax.servlet with jakarta.servlet can cause such issues.

Suggestion to release a version that supports the above mentioned environment and still supports javax.servlet.http.*.
Thank you.

@greg-db
Copy link
Contributor

greg-db commented Jun 27, 2024

Thanks for sharing this context! I'll send this along to the team to request support for this. I can't promise if or when that might be implemented though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants