NicoNes

Hey @dabbabi, Well enum are constants so that's why the names of an enum type's fields are in uppercase letters. I think the change must be done in the `jakarta.ws.rs.ext.RuntimeDelegate.HeaderDelegate`...

> There is one more catch, each @Provider now becomes a bean. While in 3.1 it was known only when registered, now in CDI the bean is there. > >...

> This feels backwards to me. CDI would not discover the jakarta.ws.rs.Application if it's not annotated. Maybe you mean if the application is defined in the web.xml, is that correct?...

Hi guys, Why not try to keep both `getHeaders()` and `getHeaderStrings()` read-only as suggested by the `view` term ? This way all response properties (headers, status, body) will be read...

@mkarg Do you have a case in mind that requires `getHeaders()` to be editable ? To my opinion, if we choose to make response `headers` modifiable we should also do...

> (1) Whether or not I personally do know such a case is not the point here. The point is that we need to be careful. If we break an...

> To me, that indicates it's mutable and a change to read-only would not be backwards compatible. Or it could also mean that `Response.getHeaders()` should not return a snapshot map...

@spericas sure you're right a summary will help. Here it is, it is a bit long but I tryied to explain all cases I had in mind: - **getEntity()** -...

@spericas > I suspect that if we write some TCKs for this, some implementations would struggle. > > I'm generally in favor of merging this, but wanted to bring this...

Hi guys, Any update on this one ? Thanks !