Apache CXF 2.4.9 is more strict in terms of message validations for security reasons. This is also required to deal with the vulnerability mentioned at http://cxf.apache.org/cve-2012-3451.html .
Unfortunately, the only real solution here is fixing the wrong message. As a workaround, though, you might want to try setting the Apache CXF soap.no.validate.parts property to true in the message context. Unfortunately, on server side that's not easily done in an effective way withouth introducing a dependency to apache cxf api; you should try adding @org.apache.cxf.annotations.EndpointProperty(key = "soap.no.validate.parts", value = "true") to your endpoint impl class.