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)?
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.wsnamespace, and at the same time it and depends onjavax.validationfor bean validation.Or sort of depends. The classes are annotated with
@javax.validation.NotNullyet I found no place with@javax.validation.Valid, no dependency on Jersey Bean Validation extension nor an explicit call to ajavax.validation.Validatoranywhere 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.NotNullannotation 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)?