Wrong SOAP 1.2 namespace added in generated SOAP 1.1 Fault

If in an SOAP 1.1 endpoint is generated a SOAP Fault (for example raising an
exception) in the Fault element is addedd a wrong SOAP 1.2 namespace.

For example this code:
@WebMethod(operationName = "operation")
public String operation()

{ throw new UnsupportedOperationException("not yet implemented"); }

will generate this response where the Envelope namespace is correct, but the
namespace declared in S:Fault is wrong (is the SOAP 1.2 namespace)

<S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"><S:Body><S:Fault
xmlns:ns4="http://www.w3.org/2003/05/soap-envelope">S:Servernot
yet implemented</S:Fault></S:Body></S:Envelope>

as the namespace is not used I don't know if it could create problems in clients
other than metro.

Environment

Operating System: All
Platform: All

Affected Versions

[2.1]

Source: https://github.com/javaee/metro-wsit/issues/1486
Author: glassfishrobot

Start with the Java @WebMethod endpoint shown in the report and reproduce the generated SOAP Fault from its UnsupportedOperationException. Trace how the SOAP 1.1 Envelope and Fault namespaces are selected. Done means a SOAP 1.1 Fault no longer declares the SOAP 1.2 namespace, while SOAP 1.2 responses remain correct.