Resteasy header in custom ContextMapper don't work - i think ?

[l.sroka]

Hello, like in title i have little test on adding custom header to rest response.
I have test it with https://addons.mozilla.org/pl/firefox/addon/restclient/ and i dont see in response headers my custom header.
Also in firebug http://127.0.0.1:8080/test/rest/api

here it is my custom context mapper:

public class MyTestComposer extends RESTEasyContextMapper{

    @Override
    public void mapFrom(RESTEasyBindingData source, Context context) throws Exception {
        System.out.println("mapFrom:");
        super.mapFrom(source, context);

    }

    @Override
    public void mapTo(Context context, RESTEasyBindingData target) throws Exception {
        System.out.println("mapTo");
        super.mapTo(context, target);      
        target.addHeader("test-my-head", "lol");      
    }
}

All simple app in attachment.

I saw in Setting headers on the request of a Client REST binding. that it is possible to add this header in custommapper.

1.  Re: Setting headers on the request of a Client REST binding.

  

       Keith Babo  

You can also implement your own context mapper to add the headers.  Or you could just set the context properties in whatever code is invoking the REST reference binding.

What i am doing wrong ?

SY version 1.1.0 with eap 6.1

[mageshbk]

You might have hit this issue:

[SWITCHYARD-1731] Properties apart from component labeled ones should be included if explicitly specified in config - JB…

Which version are you using?

[l.sroka]

SY version 1.1.0 with eap 6.1

I have also try:

        context.setProperty("Access-Control-Allow-Origin", "*").addLabels(new String[] { EndpointLabel.REST.label() }); // also HTTP tested

        super.mapTo(context, target);

[mageshbk]

You will need to add the header filter in the config like this

<resteasy:contextMapper class="com.example.switchyard.rest_switchyard.MyTestComposer" includes=".*"/>

or like this

<resteasy:contextMapper class="com.example.switchyard.rest_switchyard.MyTestComposer" includes="test-my-head"/>

regards,

Magesh

[l.sroka]

Thanks for advice but i still don't get this header in my response.
I have added as following :

<resteasy:binding.rest>

        <resteasy:contextMapper class="com.example.switchyard.rest_switchyard.MyTestMapper" includes=".*" />

        <resteasy:interfaces>com.example.switchyard.rest_switchyard.RestJson</resteasy:interfaces>

        <resteasy:contextPath>test</resteasy:contextPath>

</resteasy:binding.rest>

And in MyTestMapper:

public class MyTestMapper extends RESTEasyContextMapper {

    @Override

    public void mapTo(Context context, RESTEasyBindingData target) throws Exception {

        super.mapTo(context, target);

        target.addHeader("test-my-head", "lol");

    }

}

Also i have try:

context.setProperty("test-my-head", "lol").addLabels(new String[]{EndpointLabel.HTTP.label()});

super.mapTo(context, target);

Here is my header response (plain text from  chrome-console) without my eg. "test-my-head"

1. HTTP/1.1 200 OK Server: Apache-Coyote/1.1 Content-Type: application/json Transfer-Encoding: chunked Date: Wed, 22 Jan 2014 07:54:24 GMT

What am I doing wrong ?

[l.sroka]

bump, bump

Hello Magesh, did you test it with my example ?
Sorry to bother, but your answer is very important for me and my team.

Thanks...

[trohovsky]

Hi Lukasz,

just guessing, but doesn't work this?

context.setProperty("test-my-head", "lol", Scope.MESSAGE);

super.mapTo(context, target);

Tomas

[mageshbk]

Oops! Missed the notification that you have replied earlier. In JAX-RS, to propagate a header, you should be working with Response object and set the header there. Similarly, in SwitchYard in order for the headers to propagate, you need to design you REST interface methods with a Response as return value.

@GET
@Produces(MediaType.APPLICATION_JSON)
public Response fetchAll();

@GET
@Path("{id}")
@Produces(MediaType.APPLICATION_JSON)
public Response fetchJson(@PathParam("id") String id);

@POST
@Produces(MediaType.APPLICATION_JSON) 
@Consumes(MediaType.APPLICATION_JSON)
public Response addJson(ContractJson c);

@PUT
@Path("{id}")
@Produces(MediaType.APPLICATION_JSON)
@Consumes(MediaType.APPLICATION_JSON)
public Response updateJson(ContractJson c, @PathParam("id") String id);

[l.sroka]

I didn't notice this return type Response in any doc.

Thank you.