JacksonJsonProvider MessageBodyReader 'readFrom' returns null about jackson-jaxrs-providers HOT 7 CLOSED

(comment copied from the original bug)

Looks like the old behavior was specified in one of the drafts of the specification (and this was reported in old issue 17). Does seem to have changed in the published spec.

from jackson-jaxrs-providers.

Maybe introducing a DeserializationFeature.FAIL_ON_EMPTY_SOURCE (default false) would be an option?

from jackson-jaxrs-providers.

+1 (subscribe)

from jackson-jaxrs-providers.

Hmmh. One nasty problem with NoContentException: it is only defined in JAX-RS 2.0. So I don't think it can actually be used as we still support 1.x version for various reasons.

So what would be suitable alternative? I assume JAX-RS 1.1 should have some suggestion here.

from jackson-jaxrs-providers.

One idea... maybe I can just dynamically locate the exception class if it's there.

from jackson-jaxrs-providers.

Yes sounds reasonable.

M

Sent from my iPhone 5s

On 06 Apr 2014, at 06:53, Tatu Saloranta [email protected] wrote:

One idea... maybe I can just dynamically locate the exception class if it's there.

—
Reply to this email directly or view it on GitHub.

from jackson-jaxrs-providers.

Ok: Added JaxRSFeature.ALLOW_EMPTY_INPUT, which defaults to 'true' for backwards compatibility reasons. When disabled, error will be thrown, which should be properly translated: with JAX-RS 2.x will dynamically locate and use NoContentException; with 1.x just throws IOException with same error message.

from jackson-jaxrs-providers.