Christian Kaltepoth

@rsoika Thanks for bringing this up. I agree that the spec or the API docs should state whether `null` is allowed for the entity in the PUT case or not....

I just did a quick Google search and it looks like there are APIs allowing PUT with empty body like the [Spotify API for Play/Resume](https://developer.spotify.com/documentation/web-api/reference/player/start-a-users-playback/). Let me emphasize this again:...

Back to the original discussion. It looks like @spericas, @mkarg and I agree that we should allow `null` entities in the client API. Anyone interested in providing a pull request?...

I think JAX-RS should use the same annotation inheritance rules for `UriBuilder.fromResource` as for the server-side (which are described in section 3.6 of the spec). This would be most consistent.

I agree that the annotation inheritance rules described in section 3.6 are a bit "special" and may not be very intuitive. But changing them would be challenging in regards to...

> I've never understood why the current restrictions on annotation inheritance exist. Was there a compelling technical reason? I also wondered what the reason was to define it this way....

I like the idea. Although I must confess that I'm not fully sure if I understand all the implications.

@mkarg Just to make sure I understand correctly. So you think we should split up the API JAR into three JARs (common, server, client)? This would be a requirement for...

I agree that splitting up into common, server and client may be a good idea. Not sure if we should split up even more (for separating SSE for example). This...

Good question. Of course `ParamConverterProvider` provides more details about the "injection point" via the various parameters: https://github.com/eclipse-ee4j/jaxrs-api/blob/58a2e14c884ca9c322d158aeb8fffa875b33e27c/jaxrs-api/src/main/java/jakarta/ws/rs/ext/ParamConverterProvider.java#L48 However, in most cases you only need the raw type.