mkarg commented on issue #52: JOHNZON-281 JAX-RS Provider MUST throw NoContentException URL: https://github.com/apache/johnzon/pull/52#issuecomment-536305398 @rmannibucau Maybe I do have a vote, actually I don't know as I am not used to Apache rules. :-) We all understood your point already, no need to repeat it. JAX-RS 2.1 and JAX-RS 2.0 *are* fully backwards compatible in the sense that an application written against JAX-RS 1.1 works 100% the same on JAX-RS 2.0. Nothing breaks here, but see, there is reason why 2.0 was not simply named 1.2: Once you write a component for JAX-RS 2.x, the rules have changed, and you need to follow the new rules. And the resulting component can *only* be used by application that also follow these new rules *or stick with JAX-RS 1.x*. There is *no* guarantee in Java EE that *no changes at all* are needed, for example see CMP (Container Managed Persistency): It was simply dropped in favor of JPA, which enforced a *massive* overhaul of existing applications back then, and it broke *all* existing applications. JAX-RS 2.0 and 2.1 passed all levels of the JCP process and finally were published as official standards everbody need to follow to claim compliance. Even if you personally think this was a wrong decision by everybody involved in the standardization process, there will not be a change in the interpretation of the existing spec, only the possibility to change it in an upcoming spec (you are invited to participate in that). Also "period" ;-). BTW, it is fine if you add an option to Johnzon's MBRs that explicitly switch off JAX-RS compliance to keep backwards compatibility. We often have this situation that bugs or incompliances have to be kept, and you could follow that path, even if it means that an existing JAX-RS application has to set a Johnzon-specific config option in its bootsrap, it would be a possible solution.
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
