• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
2

Compatibility Issue with com.adobe.pdfservices and Jakarta EE's jakarta.validation Namespace

Community Beginner ,
Nov 06, 2023 Nov 06, 2023

Copy link to clipboard

Copied

 

We have recently upgraded our application to Spring Boot 3, which includes the transition from the traditional `javax` namespace to the new `jakarta` namespace as part of the move towards Jakarta EE. Since the upgrade, we have encountered a compatibility issue with the `com.adobe.pdfservices` library that we are using within our application.

Issue Summary:
Upon invoking methods from the com.adobe.pdfservices library, we are encountering a `NoClassDefFoundError` for `javax/validation/Validation`. This appears to be because the com.adobe.pdfservices library is still using the old javax.validation API, which is not available in our new Jakarta EE environment.

Adobe pdf services sdk version: 3.5.0

 

implementation 'com.adobe.documentservices:pdfservices-sdk:3.5.0'

 


Error Encountered:

java.lang.NoClassDefFoundError: javax/validation/Validation


This is causing a significant impact on our application, as we rely on the `com.adobe.pdfservices` library for critical PDF processing tasks.

We understand that the transition to Jakarta EE's jakarta.validation is relatively recent, but given the widespread adoption of Spring Boot 3 and Jakarta EE, it would be beneficial for the `com.adobe.pdfservices` library to be compatible with the latest standards.

Request:

Could you please provide information on whether there is an existing version of com.adobe.pdfservices that supports Jakarta EE, or if there are plans to release an update to address this compatibility issue? If an update is in the works, any timelines you can share would be greatly appreciated to help us plan accordingly.

Alternatively, if there are any recommended workarounds that Adobe suggests for this scenario, that would also be incredibly helpful.

TOPICS
Bug , Feature request , General , Java SDK , PDF Services API

Views

145

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Nov 06, 2023 Nov 06, 2023

Copy link to clipboard

Copied

I'm going to report this internally right now. If you have an enterprise account with us, I'd also encourage you to reach out to your support rep.

 

Also, you _could_ consider rewriting your code to use the REST API. Yes, that is a 100% 'rewrite', but keep in mind, the REST API is *incredibly* easy to use. I don't write Java, but based on my Node.js experience, the 'rewrite' is about 30 minutes of work. 

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Beginner ,
Nov 06, 2023 Nov 06, 2023

Copy link to clipboard

Copied

Thanks for the prompt reply. I will check out the REST API documentation.

I do believe that my company has an enterprise account. Where can I find information about our support rep? 

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Adobe Employee ,
Nov 06, 2023 Nov 06, 2023

Copy link to clipboard

Copied

LATEST

that i have no clue on - sorry

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Resources