Markus KARG

@rmannibucau You need to accept the truth that we will not treat it as a regression and there will not be the outcome that one can call his MBR "JAX-RS...

@rmannibucau It is backwards compatible. But it is not compliant. This is a difference.

@rmannibucau In JAX-RS there is no such thing named "parser mapper".

@rmannibucau JAX-RS 1.1 did not allow an MBR to throw any other exceptions besides `WebApplicationException` and `IOException` (see JAX-RS 1.1. JavaDocs): ``` Throws: java.io.IOException - if an IO error arises...

@rmannibucau I cannot find anything in neither JavaDocs nor Spec of JAX-RS 1.1 which proofs your claim. It might be the case that you understood it that way, and it...

@rmannibucau Unfortunately this is simply is a common misunderstanding. The spec explains all components separately in different chapters. 4.4 explains what an exception mapper does *in case* an exception is...

@rmannibucau Again we seem to misunderstand each other (English is not my mother's tongue, so maybe my arguments are not perfectly laid out). Certainly you can throw any exception you...

In line with our roadmap we should cover this in JAX-RS 3.0.

@jeyvison Great to have you on board! Please find the roadmap in our wiki. CDI will be part of JAX-RS 3.0, which is rather far away. So if you start...

> Could you please foresee in the spec all the extension/configuration points needed by a standalone client (not deployed in a EE container) to use CDI-SE? I think we could...