Robert, I'm using Flextense to generate the proxy and I'm having excellent results using the proxy to communicate with dotNet web services. The proxy generated by Flextense generate arrayCollections (denpend on how complex is your WSDL) and I had to fix the Flex SDK 3.0 XMLDecoder/XMLEncoder to make it compatible with the proxy generated by FlexTense. I submitted my fixes to Adobe bug System management for their consideration. Yes, The proxy generator shipped with Flex Builder 3 needs some work and it doesn't like SOAP version 1.2. It only generate proxy for SOAP version 1.1.
Alberto Acevedo Robert Csiki wrote: > > > This tool generates Actionscript code that is not usable at all. > > I created a very simple Web Service, deployed it and then I used this > tool from FlexBuilder3 to get the AS code in order to consume the > service. This generated proxy code is buggy and therefore is not > working, even for very, very simple services. > > Why was this feature shipped with the FlexBuilder3, if it's practically > unusable?? I can provide you with implementation details of my very > simple test Web Service. > > I really appreciate an answer here. I posted similar questions regarding > this topic before and got nothing. Thanks. Robert > > > > > -- View this message in context: http://www.nabble.com/FlexBuilder3-and-Web-Service-proxy-generation-tool-tp16986488p17085844.html Sent from the FlexCoders mailing list archive at Nabble.com.
