On 10/7/2013 4:13 AM, Marek Potociar wrote:
>
> On Sep 9, 2013, at 2:41 PM, Sergey Beryozkin <sberyozkin_at_talend.com> wrote:
>
>> On 09/09/13 13:27, Bill Burke wrote:
>>> I ran into the same problem. I didn't think we agreed on that, but when
>>> you think about it, the interceptor can change the content-type so it
>>> makes sense the writer/reader would change underneath.
>>
>> Yes, I agree, I guess Writer or Reader context implementations should be prepared to deal with the change of the properties which were used to select the currently wrapped provider, though I'd say the if the current MBR or MBW is still capable (isReadable or isWriteable still returns true) then it should be used
>
> Spec does not define anything like "current" reader/writer. IOW, the spec does not mandate entity provider to be selected prior entity interceptors are invoked.
>
And yet the TCK tests this very thing...
Bill
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com