camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gisbert Amm <>
Subject Re: Cannot retrieve header anymore after upgrading from 1.4.0 to 1.5-SNAPSHOT
Date Wed, 10 Sep 2008 16:35:11 GMT
Hash: SHA1

Hi Willem,

thank you for the quick reply. I'm afraid I don't really understand what
you want to tell me. I can see that you've commented the code in the
test that did more or less the same I did because this information is
obviously no longer provided in CXF 2.1.2.

However, what do you mean when you say I should use SOAPActionExtractor
only for handling the request message? I thought that I already did so:

<from uri="cxf:bean:MyEndpoint"/>
<process ref="sOAPActionExtractor"/>

And how can I retrieve the SOAP action from the message now? My routing
relies on it ...

Gisbert Amm

Willem Jiang wrote:
> Hi,
> Camel-1.5 snapshot is using CXF 2.1.2  and CXF 2.1.2 only apply the
> SOAPAction for the request message (in SoapPreProtocolOutInterceptor).
> Please make sure the SOAPActionExtractor only be used for handling the
> request message :)
> You can find more information in the CustomerServicesTest[1]
> [1]
> Willem
> Gisbert Amm wrote:
> I've upgraded Camel to the current HEAD from SVN.
> Consider this code, which worked fine with version 1.4.0:
> public class SOAPActionExtractor implements Processor {
> public void process(Exchange exchange) throws Exception {
>         Map header = (Map)
> exchange.getIn().getHeader(Message.PROTOCOL_HEADERS);
> ...
> (Message is of type org.apache.cxf.message.Message)
> After upgrading to 1.5-SNAPSHOT, the header is null and I therefore get
> a NPE later on. Can somebody explain why this happens and what has
> changed here? That would be very helpful.
> Regards,
> Gisbert Amm

Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla -


View raw message