Got this fixed. I was using SOAPHANDLER implementation to make changes to soap message. I was getting SOAP message converting it to string and creating another soap message from this string. The changes made this way were not able to reflect in final SOAP message so removed the logic to create a new soap message and worked with the one that soap context had.
-- View this message in context: http://cxf.547215.n5.nabble.com/The-SOAP-action-specified-on-the-message-does-not-match-the-HTTP-SOAP-Action-tp562966p5765931.html Sent from the cxf-user mailing list archive at Nabble.com.
