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

Jakarta EE used for REST, Java EE for validation #49

Open
virtual-machinist opened this issue Oct 6, 2022 · 0 comments
Open

Jakarta EE used for REST, Java EE for validation #49

virtual-machinist opened this issue Oct 6, 2022 · 0 comments

Comments

@virtual-machinist
Copy link

I couldn't help but notice that as of version 1.5 this project was migrated to Jersey 3.0.x, which uses the jakarta.ws namespace, and at the same time it and depends on javax.validation for bean validation.

Or sort of depends. The classes are annotated with @javax.validation.NotNull yet I found no place with @javax.validation.Valid, no dependency on Jersey Bean Validation extension nor an explicit call to a javax.validation.Validator anywhere in production code.

Regardless, is this a combination worth supporting? I imagine migrating from Java EE to Jakarta EE is something that ought to be done at once to highlight places needing attention. Or was the @javax.validation.NotNull annotation used for documentation/static analysis purposes and it may be replaced with something else (e.g. JetBrains annotations that are already used here as well)?

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

1 participant