Andy McCright
Andy McCright
> I am not sure about the use-case for T. Usually, we have a list of EntityParts, each of which has a different type. So we would need to get...
@spericas I'm fine with moving this to 4.0. Thanks.
I agree with @jansupol - I like the change in general, but agree that it should be deferred to the next release (3.2 if we have one, otherwise 4.0).
Hi @jimma - the `EntityPart.Builder` class is used for the multipart sender to specify the object to send and the type/generic type of that object. The `EntityPart` is intended to...
I'm concerned that it might add confusion or require language like "if on the sending side and not yet sent, returns the content, otherwise throws an IllegalStateException" or similar (once...
@erik-brangs it is probably too late to go into the 3.0 release (and might not be allowed depending on if it changes behavior), but it could go into the 3.1...
Does this potential vulnerability really matter in cases where there is no HTTP entity in the request? Or in cases where the resource method does not accept an HTTP entity?...
> As a workaround could a pre-matching request filter not be used to add a Content-Type by default? I think that that could be the strategic answer. Just enable the...
My opinion is that the JAX-RS implementation should close the input stream - so in your example, I would expect to see `Was closed? true` in the output. That said,...
> Am I in the right place to ask for a correction of small flaw in the JAX-RS API? Yep, you're in the right place. :) > Of course changing...