attached you can find a log from the WS Server comparing a call from soapUI and the non working code from tclws.

how can I configure the client to make the calls as sopaUI? I guess the mai problem is the parameter which also contains the tns1:

<tns1:projectName>MQB_B_XB16</tns1:projectName> should be <projectName>MQB_B_XB16</projectName>

###### RIGHT: ######

<inbound> <v3:setVehicleProject xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:v3="http://automation.vehiclefunction.vaudas.odis.volkswagen.de/V3.4"> <projectName>MQB_B_XB16</projectName> </v3:setVehicleProject> </inbound>

###### Wrong: ######

<inbound> <tns1:setVehicleProject xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" xmlns:tns8="http://localhost:8085/OdisAutomationService" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:tns5="http://www.w3.org/2007/05/addressing/metadata" xmlns:tns4="http://schemas.xmlsoap.org/ws/2004/09/policy" xmlns:tns3="http://www.w3.org/ns/ws-policy" xmlns:tns2="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" xmlns:tns1="http://automation.vehiclefunction.vaudas.odis.volkswagen.de/V3.4" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:d="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"> <tns1:projectName>MQB_B_XB16</tns1:projectName> </tns1:setVehicleProject> </inbound>

anonymous added on 2013-09-17 09:18:11 UTC:
found suppressTargetNS

but also had to comment out the following lines that added the xmlns which was missinterpreted by the server and lead to problems

ClientSide.tcl 2158ff:

if {[dict exists $serviceInfo noTargetNs] && ![dict get $serviceInfo noTargetNs]} { $env setAttribute "xmlns" [dict get $xnsList tns1] }