ClientResource#post different behaviors

[loicoudot]

I've configured my ClientResource to prefer JSON.
When i use this method: public <T> T post(Object entity, Class<T> resultClass) the entity is correctly wrapped in a JacksonRepresentation object by the toRepresentation internal method.
But, with the method: public Representation post(Object entity) the entity is incorectly wrapped in a JaxbRepresentation.
In the first case toRepresentation is called with getConnegService().getPreferredVariant(...) and in the second case the Variant is NULL.
Is this a normal behavior ?

[thboileau]

Hello,
in the first case it seems to work fine, but we can wonder if it's quite normal to leverage the client preferences for response's entities, even if we are about to serialize request entities.
At least the behavior is inconsistent.
Another user reports this kind of problem:

In our case the POST entity matches with a custom media type as well as
JSON. The requested result type (String[]) matches with another custom
media type and JSON as well. ClientResource chooses the JSON format over
our custom format here because that format is also one of the accepted
media types for the result. This looks like an odd choice me. I would
expect the code just to look at the scores of the variants and pick the
one with the highest score, or the first one of those if there are multiple.