jsr339-experts@jax-rs-spec.java.net

[jsr339-experts] Re: [jax-rs-spec users] The origin of MessageBodyWriter - when to check

From: Santiago Pericas-Geertsen <Santiago.PericasGeertsen_at_oracle.com>
Date: Fri, 26 Apr 2013 08:55:34 -0400

Hi Sergey,

 It's a bit difficult to comment on this without looking at the test. Is this a TCK test that you're referring to? If so, which one?

-- Santiago

On Apr 25, 2013, at 11:01 AM, Sergey Beryozkin <sberyozkin_at_talend.com> wrote:

> Hi Santiago, All,
>
> The specification says:
>
> "An implementation MUST support application-provided entity providers and MUST use those in prefer-
> ence to its own pre-packaged providers when either could handle the same request.
> "
>
> We have a failing test. An application provider, typed on Object, is written to support some specific types like Boolean, InputStream, etc, and its isWritebale & isReadable checks that a given Object is of the supported type and returns true if yes, false if not.
>
> The test still expects that the shipped/pre-packaged provider (presumably typed for example on Boolean or InputStream) is chosen.
>
> The question boils down to what is the order of the 'origin' key. Does the specification mean that it is a tertiary key ? If yes then I'm accepting the test is valid, if not - concluding it is not.
>
> Thanks, Sergey