We should fix this immediately - I'll volunteer to do so this weekend. Are people OK with switching back to the "pre-flight-check" for MU headers (my preferred fix)?
After some consideration I think this needs a bit more thought, since "pre-flight"ing requires all Handler authors to include the QNames their Handlers deal with, and also requires pre-execution knowledge of all possible Handlers in the chain. These aren't really huge problems, but they are changes and need to be carefully considered. Perhaps the first step toward fixing this is putting the MU-checking handler back at the end of the SOAPService's request chain and then going further after that.
--Glen
Ok, take tiem to think about it :)
This defect is in the shipping Axis1.1, yes?
In which case we need to notify Axis-user and soapbuilders that we are being noncompliant with the standard. Interesting that there is no test for it in the interop tests
