How to force wsclient to include missing Service XML Namespace parameter?

Can please anyone help me? (Again, sorry for the cross-post but am getting desperate after three days and nobody seems to be active in the shell wsclient forum ...) Have traced problem to incomplete SOAP Envelope tag which has a missing Service XML Namespace parameter - xmlns:ABCD="http://www.ABCD.si/ws/ABCDnet". (Original post - http://wso2.org/forum/thread/4322.) How can I force the shell envoked wsclient to build a complete SOAP Envelope tag which *includes* the missing Service XML Namespace? This is what SOAPUI shows for a successfull service consumption: {soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ABCD="http://www.ABCD.si/ws/ABCDnet"} {soapenv:Header/} {soapenv:Body} {ABCD:GetObjectRequest} {ObjectID}bbbffca219b97d9a5530f5d4f653f484792f855787a261b2204bbe24f7212334{/ObjectID} {Storage}COMPANY{/Storage} {TransferDisposition}TRANSFER_AS_ATTACHMENT{/TransferDisposition} {/ABCD:GetObjectRequest} {/soapenv:Body}{/soapenv:Envelope} TCPmon and soap-dump shows the same for shell wsclient envoked with the XML input file (that has everything between body tags) - EXCEPT for extra service parameter xmlns:ABCD="http://www.ABCD.si/ws/ABCDnet in the SOAP ENVELOPE HEADER - {soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"} Any ideas? Is shell-envoking wsclient really so exotic? ----