Refactor WSDL is mixing up Soap11 and Soap12 messages in existing testcases

In my project there already were a lot of testcases in Soap12.  Then the WSDL was extended for new features. I used the option "Refactor WSDL" to update my project.
Unfortunately all the messages in my Soap12 testcases were automatically changed to Soap11 versions.

See below beginning and end of my WSDL, which contains both Soap11 and 12 messages (in that sequence). Complete WSDL is too large to include in this topic.

<?xml version="1.0" encoding="utf-8"?>
<wsdl:definitions xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:tns="http://www.priva.nl/iocontroller/WebServicesCommissioning/CommissioningServices/1" xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:soap11="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" targetNamespace="http://www.priva.nl/iocontroller/WebServicesCommissioning/CommissioningServices/1">
................
................
<!-- Binding names Service Soap11 -->
<!-- Binding names Service Soap12 -->
<!-- Type definition of elements appearing in the methods provided by the Data service -->
<!-- definition of the SOAP messages -->
<!-- definition of how each SOAP method maps to SOAP message in and out -->
<!-- Defines how the SOAP messages and methods are rendered; defined for SOAP 1.1 only -->
<!-- Defines how the SOAP messages and methods are rendered; defined for SOAP 1.2 only -->
<!-- binds the service to a URL; note that both SOAP 1.1 and SOAP 1.2 bindings are provided -->
</wsdl:definitions>

What is causing my problem, the fact that the 11 stuff comes before the 12 stuff? Or the fact that there should be 2 separate WSDL files, one for each Soap version?
What can I do to solve my problem?

Best regards,
Rob Deenen