Christian Kaltepoth

I also think that currently, the word "view" suggests read-only behavior. And maybe making this "official" would be a good solution? @mkarg Is there any special reason for your proposal...

I don't think that there is consensus yet if the current behavior should be changed or not. Speaking only for myself: I also dislike that trailing slashes are currently ignored....

> In the end, it is _my_ fault that I did it wrong in my app, so it is _my_ job to fix it ASAP. I'm not sure if it...

I also like the idea of adding something like a simple boolean to the exception class to indicate that it was thrown from the JAX-RS client. This would allow to...

I'm fine with your proposal of enforcing the order as currently listed in the spec. :+1:

I also think it is not our responsibility to provide CDI injection for servlet classes. So I'm +1 for dropping the requirement as well.

I like the idea of adding `getParamConverter` to the `Providers` class. We already support looking up MBWs/MBRs and exception mappers this way. So adding support for parameter converters makes sense...

In my view it would be reasonable to assume that `SSLContext.getDefault()` is used by default. And I guess that this is what the spec means with "default Java runtime settings"....

> I certainly understand where you're coming from. But, every addition brings additional complexity to the algorithm and, to be honest, the benefits seem very small in this case. Most...

@spericas But wouldn't it be a good idea to clarify in the spec how such a case should be handled? Of course, we have to deal with backwards compatibility. But...