You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After I have solved my problems described in the issue #39 I have faced with the following errorString() from my queries:
Error downloading https://adatkuldes-teszt.nemzetidohany.gov.hu:8444/nd/MasterData.svc - server replied: Cannot process the message because the content type 'application/soap+xml;charset=utf-8;action=http://localhost/nd/communication/IMasterData/GetManufacturers' was not the expected type 'application/soap+xml; charset=utf-8'.
After some investigation I have figured out that the action part have to be removed from the content type and a soap:header tag have to be added to the soap envelope containing a wsa:Action element which contains the soap action.
My WSDL file contains an wsaw:UsingAddressing element in the wsp:Policy tag (which is unparsed by the kdwsdl2cpp).
I understand that the support for parsing the Policies would require a lot of work, but would not be a viable method to implement the parsing of the policies partially first by only looking for the wsaw:UsingAddressing element?
The text was updated successfully, but these errors were encountered:
After I have solved my problems described in the issue #39 I have faced with the following errorString() from my queries:
After some investigation I have figured out that the action part have to be removed from the content type and a soap:header tag have to be added to the soap envelope containing a wsa:Action element which contains the soap action.
My WSDL file contains an wsaw:UsingAddressing element in the wsp:Policy tag (which is unparsed by the kdwsdl2cpp).
I understand that the support for parsing the Policies would require a lot of work, but would not be a viable method to implement the parsing of the policies partially first by only looking for the wsaw:UsingAddressing element?
The text was updated successfully, but these errors were encountered: