Hi,
This is not the first time I knocked my head into the W(D)all trying to use Webservices, but I want to warn others so they do not spend a couple of days wondering why their webservices do not seem to work.
WinDev:
1. I Import a [site.asmx] - description file from a data vendor and this loads perfect without any errors.
2. I try to use some of the Ping/Hello type of functions supplied and they work.
3. Then I try to use a function that requires some parameters, they do not give any error it just dont return any data making me (wrongly) suspect the vendor`s database is empty or something.
4. After a couple of days where I tried everything from SoapRun, SoapRunXML and so forth (only getting errors) I have to actually get something done, and fire up Visual studio
Visual Studio
1. Import the WSDL file
2. Test functions that now work as a charm. (2 minuttes)
Question: Where in my work do the "develop 10 time faster" apply? :(
Anyway, when I have loaded the WSDL file into VS it seems I got more sub-methods, and VS seems to call these "Sub methods" depending on how many parameters I supply to a given function. WinDev defines the "GetAxaptaViewAsString" with full 5 parameters as VS lets me supply only 3, making them empty is not an option in WinDev.
So my advice is this: If you got problems with webservices that are not Super-Simple or made by WebDev, make an Webservice-DLL in Visual Studio and use this DLL in WinDev (if no problems occur using .NET DLL in WinDev)
What is surprising is that no error whatsoever are produced, it`s just not any data there - this could lead to hours (as it did for me) trouble shooting with no-luck as a result.
Picture of my (according to documentation) webservice code and execution in WinDev:
WinDev 10 times faster!! after 1 and a 1/2 day work
Then Visual Studio
2 minutes in Visual Studio
Note: Check out how many more methods are made when importing the WSDL file into Visual Studio?
I want to conclude that the WSDL parser in WinDev is somewhat buggy, or am I wrong?
Cheers
Tor-Bjarne
This is not the first time I knocked my head into the W(D)all trying to use Webservices, but I want to warn others so they do not spend a couple of days wondering why their webservices do not seem to work.
WinDev:
1. I Import a [site.asmx] - description file from a data vendor and this loads perfect without any errors.
2. I try to use some of the Ping/Hello type of functions supplied and they work.
3. Then I try to use a function that requires some parameters, they do not give any error it just dont return any data making me (wrongly) suspect the vendor`s database is empty or something.
4. After a couple of days where I tried everything from SoapRun, SoapRunXML and so forth (only getting errors) I have to actually get something done, and fire up Visual studio
Visual Studio
1. Import the WSDL file
2. Test functions that now work as a charm. (2 minuttes)
Question: Where in my work do the "develop 10 time faster" apply? :(
Anyway, when I have loaded the WSDL file into VS it seems I got more sub-methods, and VS seems to call these "Sub methods" depending on how many parameters I supply to a given function. WinDev defines the "GetAxaptaViewAsString" with full 5 parameters as VS lets me supply only 3, making them empty is not an option in WinDev.
So my advice is this: If you got problems with webservices that are not Super-Simple or made by WebDev, make an Webservice-DLL in Visual Studio and use this DLL in WinDev (if no problems occur using .NET DLL in WinDev)
What is surprising is that no error whatsoever are produced, it`s just not any data there - this could lead to hours (as it did for me) trouble shooting with no-luck as a result.
Picture of my (according to documentation) webservice code and execution in WinDev:
WinDev 10 times faster!! after 1 and a 1/2 day work
Then Visual Studio
2 minutes in Visual Studio
Note: Check out how many more methods are made when importing the WSDL file into Visual Studio?
I want to conclude that the WSDL parser in WinDev is somewhat buggy, or am I wrong?
Cheers
Tor-Bjarne