Upon further reflection, I've concluded that this isn't necessarily a bug in
the converters (they're free to return a positive score for a null target
Variant if they want), but rather a bug in ServerResource.doConditionalHandle.
If content negotation is in strict mode and getPreferredVariant()
I think it's a bug. There was a change to the JacksonConverter recently in
response to a similar-sounding report, but I don't know about the
GwtConverter. (That JacksonConverter fix is probably in 2.1-RC4.)
I remove or replace built-in converters with my own versions (that mostly
override standard
Here's my use case:
I'm submitting a conditional GET (using If-None-Match, although I don't think
that's relevant) request that also specifies a media type in the Accept header
that doesn't match any of the media types supported by the target resource
(i.e. it doesn't correspond to any of the m
3 matches
Mail list logo
