Christian Kaltepoth

I'm seeing the same issue. Clearing the site data of the browser seems to fix the issue for me. We are using v0.75.0.

@mkarg Thanks a lot for starting this discussion. I agree especially to these statements: > As everything evolves, including everybody's view on JAX-RS and HTTP in general, there is certainly...

> I share your recognition that some programmers _use_ JAX-RS as a Servlet replacement, nevertheless, as per the actual wording of the spec, still Jakarta REST _"is"_ a REST API,...

Good catch. The link should actually be: https://jakartaee.github.io/rest/apidocs/

Very interesting topic. A few spontaneous thoughts: * Currently, the behavior of the default exception mapper is not defined in detail, which leaves it up to the implementations. It would...

Please also see the discussion here: https://github.com/jakartaee/rest/issues/1147#issuecomment-1565395466

Agreed. There were a few interesting notes in the [EE4J Projects - Technical Direction](https://www.eclipse.org/ee4j/direction.php) document published about half a year ago: * Integration with CDI (see [here](https://www.eclipse.org/ee4j/direction.php#integration-with-cdi-and-config)). * Soft dependencies...

Big +1 one for this. The WADL endpoint was noted in multiple pen tests we had in the past. Having it disabled by default would be a good idea, IMO.

> So it's either Jakarta REST or just REST. The official name is "Jakarta RESTful Web Services". Jakarta REST was just a proposal at some point. At least AFAIK.

Such an exception basically means, that some component did commit the response BEFORE the ViewableWriter was invoked. Committing a response is typically caused by calling `HttpServletResponse.getWriter()` or `HttpServletResponse.getOutputStream()`. Unfortunately, this...