users@jax-rs-spec.java.net

[jax-rs-spec users] Re: Filters and Entity Interceptors

From: Santiago Pericas-Geertsen <Santiago.PericasGeertsen_at_oracle.com>
Date: Fri, 4 Jan 2013 09:48:17 -0500

Arun,

 (1) Is there some client code that triggers the reader interceptor here? Could you provide more details about your app?

 (2) What is the J1 slide that you're referring to?

-- Santiago

On Jan 3, 2013, at 8:07 PM, Arun Gupta <arun.p.gupta_at_oracle.com> wrote:

> Filters are meant for processing headers only and Entity Interceptors for HTTP bodies. Is that a good qualification ?
>
> I have a resource method as:
>
> @GET
> public String getList() {
> System.out.println("endpoint invoked");
> return "apple";
> }
>
> and the following reader and writer interceptor:
>
> @Override
> public Object aroundReadFrom(ReaderInterceptorContext ric) throws IOException, WebApplicationException {
> System.out.println("aroundReadFrom");
> return ric.proceed();
> }
>
> @Override
> public void aroundWriteTo(WriterInterceptorContext wic) throws IOException, WebApplicationException {
> System.out.println("aroundWriteTo");
> wic.proceed();
> }
>
> The invocation sequence says
>
> endpointInvoked
> aroundWriteTo
> aroundReadFrom
>
> The slides from JavaOne session seem to indicate it should be:
>
> aroundReadFrom
> endpointInvoked
> aroundWriteTo
>
> Can you please explain the sequence ?
>
> Arun
>
> --
> http://twitter.com/arungupta
> http://blogs.oracle.com/arungupta
>