Christian Kaltepoth

I don't think that we should log warnings on the client side in this situation. If the user sends an empty body with a content type, there may be a...

Yes, JSON-B is definitely a special case. It looks like we agree that the question of how empty entities should be handled cannot be defined in a generic way on...

> The problem is that this won't work, as the JSON-B API clearly says that the parser methods are only there for parsing _JSON_, but an empty stream _is not_...

> There is a difference: An empty stream is always a special case, it is _never_ valid data. As mentioned before: In the context of JSON-B: Yes, it is invalid!...

@mkarg > This will be incompatible with the JavaDocs of MBR: "_In case the entity input stream is empty, the reader is expected to either return a Java representation of...

Just to summarize a few of the arguments for supporting a wider range of schemes posted in the original thread: Pro: - The class name suggests that it is a...

No, there isn't such a plan. But you should have a look at JSR 371, which is an action-oriented web framework built on top of JAX-RS. The corresponding specification will...

I don't think that this issue is the best place to discuss your Open-EE idea. And I'm pretty sure that there won't be another name change.

@andymc12 I agree that we should deprecate `getSingletons()` in 3.0 or 3.1. So +1 for that. I'm also fine with the clarification. But I'm not completely sure if we should...

While I agree that using something like `MessageBodyContext` would have been a good idea for the MBR/MBW API, I doubt that it will be possible to refactor the interfaces this...