-
-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SOAP ENVELOPE 1.2 #14
Comments
it depends on your soap implementation. Soap versions are not just namespace changes, there are many other underlying differences. here you can find an overview. Actually the client supports both and the ose of one vs the other is defined by your wsdl schema |
And it's posible to change the version in my implementation of your soap client? The remot wsdl has this headboard: <wsdl:definitions xmlns:s="http://www.w3.org/2001/XMLSchema" xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:tns="http://www.opentravel.org/OTA/2003/05" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tm="http://microsoft.com/wsdl/mime/textMatching/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" **targetNamespace="http://www.opentravel.org/OTA/2003/05"**> |
apparently your server also supports both. you should have also two "ports" section where you can choose which one to use |
Yes, sorry for the incovenients but yes, they jave two "ports" sections. <wsdl:binding name="OTAReceiveServiceSoap" type="tns:OTAReceiveServiceSoap">...</wsdl:binding> In client Factory try this: But the message is still not correct in the construction <SOAP:Envelope xmlns:SOAP="**http://www.w3.org/2003/05/soap-envelope**"> |
Hmmm.. can you share your |
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': ~ |
Unfortunately looking at the code, the 1.2 support is not complete and there are many configuration mappings that are not complete. |
Re opeing it |
All this v0.1.3...master commits are unreleased |
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 in our company for communication with different hoteliers |
initially this lib was build exactly for OTA 😄 |
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? |
from what I can see should be good as it is |
The 'path_generator' in SoapClientExtension is new argument in config.yml. |
I changed the version of your library wsdl2php: "require-dev": { I generated the metadata and clases again. <SOAP:Envelope xmlns:**SOAP="http://schemas.xmlsoap.org/soap/envelope/"**> |
nice to hear that it worked |
Hi,
It's posible changes de namespace of soap-envelope?
WebService required:
<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">
But library put me:
<SOAP:Envelope xmlns:SOAP="http://www.w3.org/2003/05/soap-envelope">
The text was updated successfully, but these errors were encountered: