mkarg commented on issue #52: JOHNZON-281 JAX-RS Provider MUST throw NoContentException URL: https://github.com/apache/johnzon/pull/52#issuecomment-536302954 @rmannibucau Again, we did not break the behaviour, we intentionally decided that from 1.1 to 2.0 we *want* an additional exception. If you want the old behaviour, fell free to stick with 1.1 *or* simply put a clear warning in the JavaDocs explicitly declaring intended incompliance (which is fine). In the end, it is *our* decision as JAX-RS committers to define the wanted outcome of the spec, and to decide what is a bug and what is an intended change, independent of anybody's personal opinion (which is fine, too). And *this* change was *wanted* and will stay for 2.x without any loopholes or opt-outs. You can propose this change for 3.x, but this will not help *today*: The current Johnzon code still *is* incompliant and the *sole* solution is to either not declare it compliant (i. e. explicitly note the incompliance to the MBRs) or simply fix it. It is not *my* decision how Johnzon team is handling this situation. I just told you the authoritative interpretation of the spec, and I spend you some spare time for proposals how to fix it. Now take it or leave it, it is completely in Johnzon's hands, not mine. Whether Johnzon's MBRs will be compliant after whatever announced change were actually merged is to be analyzed *after* thes changes actually happend. So I will see what team Johnzon comes up with and will tell you the authoritative decision if it *then* is compliant or not. Whether you keep the JIRA ticket / this PR open or not is not my decision, but team Johnzon's. I'm not part of that, so I don't have a vote.
---------------------------------------------------------------- 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
