I was going through the FebCTP changes for WCF from JanCTP and saw the following change:
Remove MessageContractAttribute.Action (and Rely Upon OperationContractAttribute.Action / OperationContractAttribute.ReplyAction)
WCF was overriding the SoapAction if it had been explicitly declared on the MessageContract. They no longer allow you to do declare the SoapAction on the MessageContract.
This makes sense because each message you send or receive will most likely have a different action depending on the operation context. While I’m sure there are scenarios where having a standard SoapAction for a message might be useful, I cannot think of any. Do you have any valid scenarios or is this really just an edge case scenario?