overwolf

And is it possible to change the prefix: ns-8022e3d1 for an ns1 for example?

I see in YamlConverter.php In line: 150 $data["xml_root_name"] = **"ns-" . substr(sha1($data["xml_root_namespace"]), 0, 8)** . ":" . $data["xml_root_name"]; Then modifying it in the metadata will not solve the problem, will...

For example add attribute in metadatas and set it in Schema.php. xml_element: prefix: 'ns1' namespace: 'http://ws.link.hotelresb2b.com/hotel' For xml-sematics prefix should be almost irrelevant but for some clients is not the...

And it's posible to change the version in my implementation of your soap client? The remot wsdl has this headboard:

Yes, sorry for the incovenients but yes, they jave two "ports" sections. ... ... In client Factory try this: $service = $this->getSoapService($wsdl, 'OTAReceiveServiceSoap12', 'OTAReceiveService'); But the message is still not...

```yml soap_client: ~ xsd2php: namespaces: 'http://www.opentravel.org/OTA/2003/05': 'Igm\Synergy\Models\OTA' destinations_php: 'Igm\Synergy\Models\OTA': src/Models/OTA destinations_jms: 'Igm\Synergy\Models\OTA': metadata/OTA wsdl2php: metadata: 'http://vendor-ctrip.fws.ctripqa.com/Hotel/OTAReceive/OTAReceiveService.asmx?wsdl': ~ ```

OK, so I understand that doing these commits will not solve the problem, will it? If not, I could try to help you.

Ok, I will try to I'm going to try to keep an eye on him. I would like to be able to fix it because I have implemented your soapclient...

Any suggestions for which section to start looking at in order to resolve the conflict?

But would it be necessary to modify the wsdlReader true?