Hi Suvendra, If you are using the generated class with a CXF client, you should be getting the CXF's default casing, which is "SOAPAction" because it uses the same constant. Is your client really a CXF client?
But in any case, the server must expect to get the action header in several combinations, as the headers must be treated case-insensitively and there are some clients that do not use the CXF's default form. Regards, aki On Fri, Feb 25, 2011 at 3:09 PM, chakras <[email protected]> wrote: > > Thanks Aki - I was thinking it may be because my interceptor is sitting in > front of SoapActionInInterceptor - and should move it further down in the > queue. But since my workaround is working fine and I am also setting this > action back to the headers after I extract it (same code as the sample > SoapActionInIntterceptor), everything seems to be happy. > > I was wondering why I am receiving SOAPAction header in a non-standard > casing. Does this have something to do with the wsdl2java stub code > generated? Or do I need to set it manually on the headers before invoking > the stub methods? > > Appreciate your help Aki - thanks again. > > - Suvendra > -- > View this message in context: > http://cxf.547215.n5.nabble.com/SOAP-header-wsdl2java-issue-tp3399058p3400179.html > Sent from the cxf-user mailing list archive at Nabble.com. >
