Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: pass (nike.apache.org: domain of email.wtam@gmail.com designates
 209.85.221.196 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=DeraZhf160Wzz3vtubkOiFLTUakDHUs8ZJcV/t6mOL+loSE4F4B3C4rHB8T2vdj3rp
         C03WICaktQ6ejhO1czauolCh8xLnXwrUMRooHB5NZitkUtNEzOOvaXxiF6r4FHF37i+K
         9poaftzqyyEfml5Ou4G7HGWwiQlOwl8h7vQrs=
MIME-Version: 1.0
In-Reply-To: <25328913.post@talk.nabble.com>
References: <25068148.post@talk.nabble.com>
	 <eeacbf0c0908262106j58974ffbmb97b219ac225bb08@mail.gmail.com>
	 <eeacbf0c0908262138g80ff1c2w8b8d1ed3c2252474@mail.gmail.com>
	 <25195593.post@talk.nabble.com>
	 <eeacbf0c0908310827v6db66b1an8ebca7062863e03c@mail.gmail.com>
	 <25252694.post@talk.nabble.com>
	 <eeacbf0c0909020610s7a1a7081i8f23d340b63069b2@mail.gmail.com>
	 <eeacbf0c0909022127r7f2b7ac1icdbc77a9bfd5bb22@mail.gmail.com>
	 <eeacbf0c0909040756k6d8ef724j8d7675e06aa64491@mail.gmail.com>
	 <25328913.post@talk.nabble.com>
Date: Mon, 7 Sep 2009 09:15:24 -0400
Message-ID: <eeacbf0c0909070615s26a602a7jd6e67085209eb962@mail.gmail.com>
Subject: Re: setting soap headers in camel cxf router
From: William Tam <email.wtam@gmail.com>
To: users@camel.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi Kavita,

ResponseContext map is a CXF implementation detail.  CXF client puts
information related to a response in that map.  The map is eventually
copied to the CXF response message.

I took another peek at camel-cxf code,  I don't expect the response
context to be null in normal code path.  It sounds like some exception
might have happened or the Camel message is not the right message
(i.e. it may not be the response message).  Do you see any error
messages in the log or anything suspicious?  If the message is not a
response message, getting the Header.HEADER_LIST from it won't give
you to right headers obviously.

It is a bid hard for me to see what's going on.  If you could provide
a little test case, I'll be glad to take a look.

Thanks,
William


On Mon, Sep 7, 2009 at 7:21 AM, kav m<kavita.misra@med.ge.com> wrote:
>
> Hi William,
>
> Thanks a lot for putting up the test case and also updating the CXF Wiki.
> I am having a POJO based camel-cxf service endpoint [details same as triv=
edi
> has put in this thread] and trying to set soap headers so that those can =
be
> displayed in the soapUI client.I was using =A0camel-cxf 1.6.0 but after
> reading your post, I am using camel-cxf 1.6.2
>
>
> I followed the code you have written in the wiki but on line no. 2 below =
, I
> get a null responseContext:
>
> =A0CxfMessage message =3D exchange.getIn().getBody(CxfMessage.class); //1
> =A0Map responseContext =3D
> (Map)message.getMessage().get(Client.RESPONSE_CONTEXT); //2
> =A0List<SoapHeader> soapHeaders =3D
> (List)responseContext.get(Header.HEADER_LIST); //3
>
> Can you tell me what this responseContext Map is and why am I getting it =
as
> null ?
>
> Since a null responseContext did not allow me to proceed further with the
> solution, I used the following code to ultimately obtain a List of
> soapHeaders-
>
> =A0CxfMessage cxfMessage =3D exchange.getIn().getBody(CxfMessage.class)
> =A0Message message =3D cxfMessage.getMessage();
> =A0List<SoapHeader> soapHeaders =3D (List<SoapHeader>)
> message.get(Header.HEADER_LIST);
>
> The rest of the code I used is exactly what you have in the wiki. Still I=
 do
> not see any headers at all in the SoapUI client. [WS-Addressing is set to
> true in SoapUI]
> Besides the header I also need to set a POJO in the SoapBody which should=
 be
> displayed in SoapUI. I am doing that using the following code and it is
> displaying perfectly fine.
>
> exchange.getOut().setBody(subscribeResponse);
>
> Please help me to also set the SoapHeaders in the response, so that they =
are
> visible in SoapUI along with the body.
>
> Thanks for your help.
>
> Regards,
> Kavita
>
>
>
>
>
>
>
> William Tam wrote:
>>
>> Hi Trivedi,
>>
>> After chatting with Willem a bit, I realized that the
>> InsertResponseOutHeaderProcessor should have been getting the "in"
>> message as opposed to the "out" message from the exchange since the
>> processor is in the pipeline.
>>
>> That is,
>>
>> =A0 =A0 =A0 =A0 =A0 =A0 CxfMessage message =3D
>> exchange.getIn().getBody(CxfMessage.class);
>>
>> I will update the test and just want to be aware of it.
>>
>> Thanks,
>> William
>>
>> On Thu, Sep 3, 2009 at 12:27 AM, William Tam<email.wtam@gmail.com> wrote=
:
>>> Hi Trivedi,
>>>
>>> You can now find some samples in this test module:
>>> https://svn.apache.org/repos/asf/camel/branches/camel-1.x/components/ca=
mel-cxf/src/test/java/org/apache/camel/component/cxf/soap/headers/CxfMessag=
eHeadersRelayTest.java.
>>> =A0Its Camel context definition is here :
>>> https://svn.apache.org/repos/asf/camel/branches/camel-1.x/components/ca=
mel-cxf/src/test/resources/org/apache/camel/component/cxf/spring/message_he=
aders_relay.xml
>>>
>>> The test of interest is
>>> testInoutOutOfBandHeaderCXFClientRelayWithHeaderInsertion and the
>>> route that the test references is:
>>> <route>
>>> =A0<from uri=3D"cxf:bean:routerRelayEndpointWithInsertion"/>
>>> =A0<process ref=3D"InsertRequestOutHeaderProcessor" />
>>> =A0<to uri=3D"cxf:bean:serviceRelayEndpointWithInsertion"/>
>>> =A0 <process ref=3D"InsertResponseOutHeaderProcessor" />
>>> </route>
>>>
>>>
>>> Please note that the InsertResponseOutHeaderProcessor requires bug fix
>>> for (https://issues.apache.org/activemq/browse/CAMEL-1983). =A0I have
>>> submitted a fix the 1.x branch. =A0InsertRequestOutHeaderProcessor does
>>> not require any fixes.
>>>
>>> Cheers,
>>> William
>>>
>>>>>>>> Hi William,
>>>>>>>
>>>>>>> I am using Camel 1.x, can you provide me a sample how to set header=
s
>>>>>>> in
>>>>>>> Exchange for POJO based CXF webservices?
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Trivedi
>>>>>>>
>>
>>
>
> --
> View this message in context: http://www.nabble.com/setting-soap-headers-=
in-camel-cxf-router-tp25068148p25328913.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
>