You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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)?
The text was updated successfully, but these errors were encountered:
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 onjavax.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 ajavax.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)?The text was updated successfully, but these errors were encountered: