Hello all, Here are some news on my experiments on web services (driven by wsdl files)
As a reminder, what I wanted was not to have something generic for all possible wsdl but to generate a kind of class model from the wsdl file of our engineering school planing application. This is kind of working now. But be aware this is a very very personal implementation not usable for others right now (but it might be in the future). The wsdl (client) part I have for now might be useful for others but I doubt this is the case right now (needs to be more generic). Actually I started in the debugger with my particular wsdl files and then developed iteratively (so wsdl stuff can be fun too :) ) . During this process, I finally get more knowledge on wsdl "technology", so it might be doable to make it more generic. I have identified some model weaknesses in it that I need to fix (refactor) and then I'll try to reproduce the process with other wsdl files when I'll have some free time. There are plenty over there (http://www.xmethods.net/ve2/index.po). For now, I'm more concerned on how to use SOAP and I'm just a bit stuck at the moment with the use of SOAP Opera (which I terribly hacked to make it kind of work). (1) I'd like to replace the use of KOM with ZnHTTPComponent - authentication doesn't seem possible natively (but I might be wrong there) -Soap Opera and Kom looks quite intermingled at the moment >> Sven: have you looked at SoapOpera ? Do you think it can be decoupled easyly >> from Kom to use ZnHttpComponent instead ? (2) the typing system is not implemented (I have a naive object wrapper on them - XSDSimpleType and XSDComplexType + XSDRestriction). - I gave a look at Brenda Larcom implementation of XSD (X Files project on squeaksource - it's MIT even if not specified yet) - I think I need a (clever) way to link XSDSimpleType/XSDComplexType with both my "wsdl" model and the soap implementation and of course map them back and forth with Smalltalk classes >> Any comments/idea here would be greatly appreciated ;-) - The "typing >> system" seems really important to me in term of interoperability with the >> outside world, but I'd like a clever way to have them mapped to smalltalk >> class/objects Thanks in advance for your comments (to me I think we need, a SOAP decoupled from KOM and XSD stufs) Cheers, Cédrick ps: the project is in squeaksource (iWSDL), but keep in mind this is a very very early stage...
