Markus KARG

I wonder why you not simply ask to make `equals` *work correctly*?

I think it would be worth letting the committers discuss that. ;-)

This bothered me a lot of times and have no clue at all why it was done so complex. Big +1 for Sebastian's proposal!

> How's an implementation going to find the _correct_ `ParamConverter` after type erasure? We could either mark the *correct* converter with an annotation having its type as an attribute, or...

First step to convince the community of such a change would be to write more about why you think this commonly is nededed / what the general benefit is. :-)

> Or adding `@Path` as a bean defining annotation. With CDI in the picture, there are enough tools for a library built on top of JAX-RS to do this unwrapping...

@gorlok What is your proposal how the JAX-RS Spec, API, JavaDocs, and / or TCK shall be changed?

> IMO the default media type of `application/octet-stream` is a great choice and makes sense to me. I don't fully understanding the restriction to `text/plain` for boolean, character and number...

> My interpretation of 4.2.4 is that the standard message body writer for `String` effectively behaves like it defines `@Produces("*/*")`, which would lead to `application/octet-stream` for the response. In conjunction...

Good catch! So while I personally would prefer to always use 400, I am okay with 404, too. So we do not need to change anything, if everybody is fine...