Cart
[Home] [By Thread] [By Date] [Recent Entries]
I've used Visual FoxPro's features to generate WSDL and create a web service. I've not done a lot with it except to test it but it makes the process drop dead easy. On the other hand, unless one can actually read the WSDL it generates, one can get [expletive deleted] into that black hole. This to me is like people who claimed HTML was so good, they should never have to understand what the DOCTYPE was for, shouldn't have to worry that they created mal-formed files, and so on. Ease is seductive and productive but without understanding, it is hard to know what the next best thing is. Remember all the articles squealing about XML as the death of the web through balkanization? I'm not afraid of balkanization. I'm afraid of ossification. len -----Original Message----- From: Mike Champion [mailto:mc@x...] I've lost track of meandering of this thead, so this may or may not be a response to my suggestion for staying away from the proprietary wizard tools for building web services. I'm not sure which side you're on here, but FWIW the argument isn't so much against the GUI tools to make life easier for real, overworked people, but against specs, or designs, or APIs or whatever that FORCE real people to use the GUI because the underlying complexity is too ugly to comprehend. SOAP hasn't reached that point yet, so I'm suggesting that if people do use VisualStudio.NET to generate their SOAP/WSDL/etc. code, that they make VERY sure that they haven't got [expletive deleted] down the lock-in black hole. ----------------------------------------------------------------- The xml-dev list is sponsored by XML.org <http://www.xml.org>, an initiative of OASIS <http://www.oasis-open.org> The list archives are at http://lists.xml.org/archives/xml-dev/ To subscribe or unsubscribe from this list use the subscription manager: <http://lists.xml.org/ob/adm.pl>
|
