Hi, Can someone tell me why SoapActionInHandler overwrites the operation that AddressingInHandler in handler may have found. Think of the case where there is a message being sent - there is ws-addressing, someone tampers with the headers (not signed) to alter the soap action, the AddressingInHandler does the correct thing - sets the operation from the soap addressing, but the SoapActionInHandler comes along and messes this up by taking the SOAPAction from the http header and overwriting the operation if one exists.
Has anyone come across this problem? Is there an easy fix for this? I can see how I would fix this in XFire's code base, but is there anyway to override the (bad) behavior of the SoapActionInHandler without altering XFire's code base? Regards, Adrian
