HTTP/1.1 200 OK
Content-Type: application/soap+xml; charset=UTF-8
Content-Length: 508
Connection: close
<?xml version="1.0" encoding="UTF-8"?><soap:Envelope soap:encodingStyle="http://www.w3.org/2003/05/soap-encoding" xmlns:soap="http://www.w3.org/2003/05/soap-envelope" xmlns:soapenc="http://www.w3.org/2003/05/soap-encoding" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><soap:Body><SessionCreateResponse xmlns="http://www.otrs.org/TicketConnector/"><SessionID>93gUJnw5fa9EaZzs59B1FBvwV4re2V1o</SessionID></SessionCreateResponse></soap:Body></soap:Envelope>
But OTRS.OTRS_SessionCreateResponse res = tst.SessionCreate(sc) always return null. As far as I understand something is wrong with WSDL file. But I can't find the mistake.
you should not trust on automatic code generation but do the coding yourself instead. You can find an example perl code on the same place like the WSDL file
"Production": OTRS™ 8, OTRS™ 7, STORM powered by OTRS
"Testing": ((OTRS Community Edition)) and git Master
Never change Defaults.pm! :: Blog
Professional Services:: http://www.otrs.com :: enjoy@otrs.com
Manual SOAP XML parsing which responses by OTRS is not right decision. It works, but it's wrong way.
In this case I don't understand for what purpose wsdl file was created.
I saw several examples of using SOAP web interfaces at different languages and they use manual SOAP XML parsing without using WSDL file.
Also I used tool SOAP UI which is Java based to debug responses and deserialization is also wrong.
In C# I saw that names of classes generated from WSDL file differ than names which is responded by OTRS.
Good afternoon. I know how to solve your problem. All the matter in the tag selection in the contract. It is necessary to rebuild the proxy under another parser. Contact me and I will explain everything in detail.
<<Добрый день. Знаю как решить вашу проблему. Все дело в теге выбора в контракте. Нужно переформировать прокси под другой парсер. Свяжитесь со мной и я все подробно объясню.>>
Just for any case. I had tried to use recommendation from the article http://www.edinkapic.com/2013/06/callin ... m-net.html at the beggining of my experiments. I generated wrapper using SVCUTIL.EXE /wrapped /serializer:XmlSerializer GenericTicketConnector.wsdl but, unfortunately, I coulddn, find suitable namespaces in created *.cs file. In attached zip file Reference files generated by Visual Studio (Reference_old) and by SVCUTIL.EXE (Reference.new).
Another command line recommendation was generation from wsdl URL: svcutil /wrapped /serializer:XmlSerializer http://wsdl_url/
but I used generation from local wsdl file.
You do not have the required permissions to view the files attached to this post.
I managed to fix your issue. Herewith I have added the code. But this only works for CreateTicketResponse, you might have to change other parts of the code accordingly.
What changes I made
Added the correct namespace
Modified the order according to the soap response by Fiddler
I wrote short article http://www.bizkit.ru/2015/02/24/2614/ where described problems with WSDL file and some recommendations. I still have some problems with several properties in OTRS_TicketGetResponse_Ticket class, and can't find suitable decision.
Yes, I placed properties corresponding SOAP response sequence. Today I found mistake, create new WSDL file and renew zip file in my blog. It properly returns all values which return OTRS for OTRS_TicketGetResponse_Ticket class. Unfortunately in SOAP response is missed Article property (OTRS_TicketGetResponse_Article). I don't know why.
Where to get all classes properties and sequence? The OTRS developer documentation is missed some of properties and there is no sequence (order) description at all.
I have created in GitHub request to merge current WSDL file with my fork.