VBZeep is completely unrelated to the "Zeep: Python SOAP client" which it predates by many, many years.
VBZeep is basically some "abandonware" - code I was developing over 6 years ago but never got around to completely finishing and certainly never got around to cleaning up. Ideally the numerous ZeepXXX classes within it would have been radically cleaned up and then moved into a separate DLL Project.
Rather than just let it continue to molder away in my backup server I thought I might throw it out here for others to take a look at. After all, though it has many small things that are incomplete it does work after a fashion - at least with some kinds of SOAP services.
If nothing else it might help others understand a little more about SOAP and why most people have completely abandoned it in favor for RESTful and REST-like techniques that don't have all of the horrible issues of SOAP.
The VBZeep Project attached contains Zeep itself (those classes) wrapped up in a "testbed" Project with a user interface. This VBZeep testbed has a settings.dat text file that contains its main window size and position as well as a list of some known web services to test against. That list gets loaded into a ComboBox at the top of the Form.
Sample run:
![Name: sshot1.png
Views: 43
Size: 11.6 KB]()
![Name: sshot2.png
Views: 36
Size: 8.7 KB]()
Take a look. Have fun. Cringe at the very rough code, and the gymnastics required of an interpretive SOAP client.
One thing not attempted in VBZeep is generation of SOAP Proxy classes to be compiled into VB6 applications. But as far as I can tell few people ever bothered to do that even using the old unsupported Microsoft SOAP Toolkits anyway.
Almost everything needed to create proxy classes after digesting a WSDL is here though. But note that Zeep doesn't handle all of the kinds of WSDL that exist and doesn't handle any of the advanced kinds of SOAP security and authentication.
VBZeep is basically some "abandonware" - code I was developing over 6 years ago but never got around to completely finishing and certainly never got around to cleaning up. Ideally the numerous ZeepXXX classes within it would have been radically cleaned up and then moved into a separate DLL Project.
Rather than just let it continue to molder away in my backup server I thought I might throw it out here for others to take a look at. After all, though it has many small things that are incomplete it does work after a fashion - at least with some kinds of SOAP services.
If nothing else it might help others understand a little more about SOAP and why most people have completely abandoned it in favor for RESTful and REST-like techniques that don't have all of the horrible issues of SOAP.
The VBZeep Project attached contains Zeep itself (those classes) wrapped up in a "testbed" Project with a user interface. This VBZeep testbed has a settings.dat text file that contains its main window size and position as well as a list of some known web services to test against. That list gets loaded into a ComboBox at the top of the Form.
Sample run:
Take a look. Have fun. Cringe at the very rough code, and the gymnastics required of an interpretive SOAP client.
One thing not attempted in VBZeep is generation of SOAP Proxy classes to be compiled into VB6 applications. But as far as I can tell few people ever bothered to do that even using the old unsupported Microsoft SOAP Toolkits anyway.
Almost everything needed to create proxy classes after digesting a WSDL is here though. But note that Zeep doesn't handle all of the kinds of WSDL that exist and doesn't handle any of the advanced kinds of SOAP security and authentication.