Hi All, Recently Raphaël Barrois pointed out and submitted a fix for a bug in the wsdl generation. This bug happens when multiple services are passed to the soaplib Application. What is happening is that all of the services are being assigned to the same service and portType.
See Raphaël's message here: http://mail.python.org/pipermail/soap/2011-March/000432.html This has come up previously in some discussions on-list with Tres Seaver. However, I had chose not to address it directly because any change to the default behavior **will** break the interface(WSDL) you have with any current consumers of your web services. Instead, I added some attributes to DefinitionBase as well as a parameter to @soap(...) to allow you all to declare explicitly which Service and PortType your DefinitonBase classes and their web methods belong in the wsdl. Nevertheless, I haven't done a particularly good job at promoting or documenting this other than through tests in the repo. I'd like to get some user feedback on how I should approach this behavior. A) Apply Raphaël's patch and by default all DefinitionBase classes will hint to the the wsdl generator that a new service should be created using the classes name by default. B) Leave the default behavior in place. I plan to improve the documentation to show a clear example of using the service and portType attributes regardless of the approach. Please reply to this on-list if you have an opinion in the matter. _______________________________________________ Soap mailing list [email protected] http://mail.python.org/mailman/listinfo/soap
