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.
On 9/9/2013 8:06 AM, Sergey Beryozkin wrote:
> Hi All,
>
> One thing which was agreed earlier was that ReaderInterceptor or
> WriterInterceptor are run only after a relevant MBR or MBW has been
> selected.
>
> Given this fact, can Reader or Writer interceptor effectively 'lose' the
> initial MBR or MBW they wrap by updating the class of the entity, etc ?
>
> For example, I'm seeing a number of early TCK tests where a provider say
> for List has been selected, the readers wrapping this List provider are
> invoked, the entity class is changed to LinkedList and thus the
> initially wrapped List MBR is expected to be ignored and a new
> LinkedList MBR invoked.
>
>
> Thanks, Sergey
--
Bill Burke
JBoss, a division of Red Hat
http://bill.burkecentral.com