I could, but first I would prefer to get feedback about what should be expected, because I'm not an expert in SOAP and I'm not clear when it is then needed to use AxisOperation for the SoapAction… Actually I'm not even clear if the WSDL's SoapAction is available from code through the AxisOperation or through the MessageContext (i.e. the Option object)… I'm currently taking over on big base of code using Axis, so I'm not even sure if it was coded correctly with respect to how Axis is meant to be used, but I can put a bit of my time to help fixing this issue.
In terms of requirements:
To me, if there is no soapAction defined in the WSDL or if there is an empty value is the same thing: a empty soap action should be sent.
For SOAP 1.2, it is the specs that says so.
For SOAP 1.1, no soap action is considered invalid WSDL: I would say it's better to follow SOAP 1.2 spec on that, but maybe that's where you thought we should use the AxisOperation as the soap action?
So to fixes this, I'm not sure where it should really happen… but if it has to be in CommonsHTTPTransportSender and these requirements I wrote are correct, I can give it a shot.