Diese Seite mit anderen teilen ...

Informationen zum Thema:
WinDev Forum
Beiträge im Thema:
Erster Beitrag:
vor 2 Jahren, 2 Monaten
Letzter Beitrag:
vor 3 Wochen, 3 Tagen
Beteiligte Autoren:
Tor-Bjarne, Peter Holemans, DM-2, Bart VDE, DerekM-2

WinDev Webservices import of WDSL File is bugged.

Startbeitrag von Tor-Bjarne am 28.04.2016 14:34


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.

1. I Import a Http://site.asmx?WSDL - 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?



Hi TB,

Indeed, I've been fighting quite a bit with using web services since V17 of WX and although it works for most simple (and public) web services it can become very cumbersome in real enterprise life with more complex and authenticated web services.

Although this type of dev (even between WX platforms wanting to use the same core backend business and data layer) is part of any future-proof environment PCSoft still has some catching up to do in this area. I found their wsdl parser far from getting up to the same level that can be found in many other commercial development platforms (MS/Oracle/...) or even open source ones.

Also their paranoia on shutting down a lot of stuff that is openly available in other platforms (import code/export code/introspection/...) makes me crazy and makes development often 10 times slower compared to any other tool... E.g. Over the years I have built my own class generator that spits out base business classes including their members and methods into txt... Next in WX there is the incredible productive part of creating an empty class in the editor, copying the declaration from the txt file into the class declaration, save, create a new method in the editor copying its name from the text file, save, copying the method code from the text file into the editor, etc... and keep on doing the same shit for every method of the class (and in my case there at least seven)... HOW PRODUCTIVE :mad: ???

In any other dev environment you can load the text file as a source file but oh no, not in WX... I guess they don't want real productive developers and only they know why. Anyway they certainly don't listen to their customers as I am requesting this feature for about 4 or 5 years now with every new version coming out. Oh! That reminds me: I still need to reraise this yearly request for V21 :rp:

Simply my 2 cents,

Peter Holemans

von Peter Holemans - am 28.04.2016 16:32
Hi Peter

Can understand your frustration. We generate a lot of class files (for Delphi) and after that it's just a matter of copy paste the code in the project. In WD you can't even read your own sources outside the environment or if the version doesn't match.
Money makes the world go 'round I guess.

von Bart VDE - am 28.04.2016 17:10
Hi Peter,

Yes it`s a bit frustrating - now I`m on the clock invoicing my client for my work, and I dont think I can charge for my struggle with the Webservice so I`m loosing money.

Other developers are also working against the same webservice in Visual Studio and they get the job done, where as I scratch my head leaving only white dust of frustration over my keyboard.

(at least I hope the white stuff is frustration ;) )


von Tor-Bjarne - am 29.04.2016 06:41
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)

Really good advice. Using WD22. I thought - this *must* work.

2-3 weeks later I have learned that with SoapUI, Fiddler, and endless patience and determination, there is still not a chance in hell of getting WinDev to do what can be done "out of the box" with dotnet.

I'm not happy about this. I wasted so much time/money trying to use a third-party service. All the simple stuff works straight away, but multiple parameters and injected XML - forget about it!

Pity. I assumed (ha ha) - that this is the one area that PCSoft would have put in a big effort,


von DerekM-2 - am 19.06.2018 23:44
What did you expect?

The 923 other new gadgets instead of real interoperability and openness towards this brave new connected world we're living in got all attention again...

I gave up a long time ago... Even doing (Negotiate/Kerberos) authenticated REST API webservices (e.g. onto a SharePoint environment within a corporate domain) seems impossible… As long as it is basic (or solely developed with WX) it works out of the box. Basic authenticated corporate web service functionality is 1000 times faster to implement in C# (with even less lines of code) and near to impossible to implement with WX. I really tried… Can you give me an example of any corporate environment that is running its business only on isolated/siloed business applications in 2018? WX is so old school in this area...

Anybody tested authenticated (Negotiate/Kerberos/NTLM) REST/SOAP web services with V23 onto SharePoint (REST should work but it seems impossible to be able to do the authentification for on-prem SharePoint web services authenticating over Kerberos/NTLM) ? Also, did anybody check if we can do XML injection into a SOAP parameter (ComplexType) of a web service or do the 'I-know-what-is-good-for-you' guys and girls at Montpellier still encode it, causing the web service execution to break? I really would be interested if anything of this improved in V23 but I'm quite afraid it isn't. I might come back to WX for some niche development I have in mind, but I'm not going to invest without having at least a clear answer on this.

As shown however by the example of Tor-Bjarne (and as I can confirm out of experience), Visual Studio is way easier to get web service interoperability done in a couple of minutes time, so there is no real reason to come back for now...


Peter H.

von Peter Holemans - am 20.06.2018 12:36
Hi Tor-Bjarne and Derek,

I'ld be interested to know if you ever raised these issues with PCSoft Tech Support?

I've been fighting with TechSupport on the XML-Injection (ComplexType parameter) issue for more than 6 months on V19 and V20 sending WX and VS projects showing off how it works in standard .Net (with less lines of code) and completely doesn't work in WX because the engine encodes the XML as an XML-String.

Finally they closed the ticket as not being a bug but an enhancement request. (WTF???) Seems that 3 years later it still is an 'enhancement request'... Either they can't read English or I can't but I'm glad to hear I'm not the only one having complained on this half baked web services stuff of PCSoft...

And then we haven't even discussed the other web services shortcomings like using web service methods with multiple signatures (variable nr. of parameters) and classical basic domain authentication (negotiate/Kerberos/ntlm) when using web services which is still impossible and takes 3 lines of code in C#...

Any future proof development will be based on (authenticated) http(s) based web services (SOAP/REST/…). Guess something went wrong with the English-French translation...

I'ld be really interested to know who also raised tickets on the completely flawed PC$oft web services interpreter/engine/…


Peter H.

von Peter Holemans - am 21.06.2018 12:37

Those skinny french developers (often pictured in their brochures) probably work for food, and I do not want to impose more work on them as they are probably to busy making the next version with a zillion new features in it. - They need to eat man!

After I discovered that reported bugs tends to be in each new version of WX (that`s at least constant) my guess is that the QA Department starved to death and that`s the reason why there are fewer girls in the brochures with this version.

This is also why there`s no known bug list, or bug reporting system.

So, you should not report bugs at all, as you with this action actually take food out of starving hands.

But I do not want to go the M$ route as M$ has shown before how they can drop a product with out thinking about numerous developers (as they did with Visual Basic)

And I actually having problem installing .NET Framework v4.7.2 on a VM and therefore I cant install the software dependent on this framework to, this halts my install process.- I like to be (as much as possible) in control over the run-time framework.(as with WinDev, Clarion etc.)


von Tor-Bjarne - am 21.06.2018 18:45
Yeah - the more I think about this - the more it seems that if PC Soft may have run its course. Happens to all sorts of software, eventually.

They could fix this - but I'm not holding my breath.

Instead of pissing into the wind, I have to live with ugly WX/.Net orchestrations. In the longer term - might as well just use .Net.

von DM-2 - am 21.06.2018 22:23
Zur Information:
MySnip.de hat keinen Einfluss auf die Inhalte der Beiträge. Bitte kontaktieren Sie den Administrator des Forums bei Problemen oder Löschforderungen über die Kontaktseite.
Falls die Kontaktaufnahme mit dem Administrator des Forums fehlschlägt, kontaktieren Sie uns bitte über die in unserem Impressum angegebenen Daten.