No it doesn't. You see the SoapActionOutInterceptor appends ";action=blaBla"
to the content-type header :
String ct = (String) message.get(Message.CONTENT_TYPE);
if (ct.indexOf("action=\"") == -1) {
ct = new StringBuilder().append(ct)
.append("; action=").append(action).toString();
message.put(Message.CONTENT_TYPE, ct);
}
where after that SoapPreProtocolOutInterceptor resets it to the string
without the action :
message.put(Message.CONTENT_TYPE, soapVersion.getContentType());
On Tue, Aug 5, 2008 at 6:16 PM, Daniel Kulp <[EMAIL PROTECTED]> wrote:
> On Monday 04 August 2008 5:07:28 pm Iman Rahmatizadeh wrote:
> > Hi,
> > As I'm playing with cxf to understand its internals, After calling a
> > service(foreign non cxf) , It gives me an exception which tells me I need
> > to supply the soapAction in my header. Digging & debugging through code I
> > see SoapActionOutInterceptor setting it in one place and later on
> > SoapPreProtocolOutInterceptor resetting to the previous value, removing
> the
> > soapAction from request headers. Something tells me I'm missing something
> > big, anyone could shed some light ?
> >
> > Iman
>
>
> I don't see the SoapPreProtocolOutInterceptor setting any sort of
> SOAPAction.....
>
> That said, I'm not sure why those two are separated out. They probably
> could/should be combined into a single interceptor.
>
>
> --
> Daniel Kulp
> [EMAIL PROTECTED]
> http://www.dankulp.com/blog
>
