Markus KARG

As `UriBuilder` is a *builder* we should discuss how to actively support *building* such non-HTTP-URIs. Are new methods needed? If *not*, what is the sake of using this class?

+1 for deprecating this method in favor of CDI

+1, but maybe we should keep 2.1 as-is?

The question is, why a server runtime injects `UriInfo` while a client runtime does not? As the invocation of the MBR on the client is a reaction upon a request...

> @chkal If Jakarta EE specs are going to change their namespace/package, that will break backwards compatibility anyway. So, isn't it the perfect (and only) opportunity to fix some methods...

@chkal No problem, just go ahead. The more opinions the better. :-)

@rmannibucau Empty streams are not "wrong" by design, so no, the empty representation is not just a "fallback", but actually is the expression that the MBR decided that it is...

@chkal Some background: Romain and I moved this discussion over from the original bug report at Johnzon, as it would be OT there. See https://github.com/apache/johnzon/pull/52.

> So could you perhaps explain a bit more why you think that this is problematic? Basically his claim is that Johnzon's several MBRs are JAX-RS 2.0 compliant and he...

Just checked the history: Actually `NoContentException` was not added in 2.1, but in 2.0 already. So it is even more years in the spec.